Wait! Looks like we don't have enough information to add this to bug database. Please follow this template bug format
SA2.2:908 - locked filter search derp
Architect 2.2.0 Build 908
Touch 2.1.1 Project
OSX 10.6.8 Develop machine accessing remote Linux VM with project/files.
Problem occurred this way (reproducible by same sequence):
- Unexpected error occurred: "Uncaught TypeError: Cannot read property 'dom' of undefined."
Limitations of issue:
- enter value into filter
- lock filter
- cursor navigate through project inspector
- error does not occur during Code view.
- can be ignored/dialogue box closed without further complications
Is this specific to your project or can you reproduce in a brand new project?
And more specifics, are you locking the filter by pressing the right arrow and enter? or by clicking the lock icon?
When you navigate to the project inspector are you doing that with TAB on the keyboard? are you clicking there and pressing up/down?
I believe this can be marked as resolved, else flag for improvement in dialogue reference.
In trying to reproduce the error using alternative navigation methods you've presented, I was also unable to reproduce the error using the method that previously was consistent for reoccurrence.
Real cause of error:
- all click methods used before - click icon, click item under view tree, then cursor navigation
- I believe keyboard shortcuts would have still led to the same outcome
Basically, seems Architect was sending its feelers down through the code looking for my search pattern and touched something confusing. The original trigger for this error message could easily have been from navigating over another View and it simply taking time to pop up a message.
- A Store on a select was incorrectly applied in another part of the project
- Since correcting this selectfield, the project actually works and the "bug" this report mentions no longer is reproducible.
If it helps, I'll mention the details of the project which caused this problem. Most of this project was originally created by someone with ST1 coding knowledge, bludgeoning code into SA2.0 until it worked. Multiple selectfields are without a Store and are populated by means such as listener functions. One of these selects I'd added a store which appeared to match perfectly, then proceeded to decipher the code regarding this select, to then apply other reqs. I eventually found a commented function with a complaint that setValue was broken, and this "feature" of the code was disabled until Sencha gets it right. I'd scoffed at the comment, thought about how it does work when coded correctly, saved the project and headed off for easter. I hadn't removed the store from this hidden selectfield, and had forgotten about it until Architect starting complaining.
Side note: I originally had typed the entire bug report using the template. This was the first occasion I'd used this forum's insert image. The popup is very similar in design to one I use with WordPress, in which I drag and drop image into the panel and it handles the rest. This of course fired the standard browser response of load image. Back presented me with not the detailed report I'd typed, but new blank thread.
Thanks for the detailed response as to what occurred.
Originally Posted by Greg Arnott
Sounds like as you selected something in the project inspector it was rendering that component in the canvas and thats when the error occurred. If you are able to isolate a small project with the hidden selectfield and the store incorrectly applied we'd appreciate it. It sounds like this may be a bug in the framework that we'd like to fix.
Originally Posted by Greg Arnott
Re: the forum issue, i've passed it along to Mitchell who runs our forums. Thanks again.