This content has been marked as final. Show 7 replies
Which line of code is causing the error?
Also states can be difficult. I'd advise using ViewStack for this complex a change.
I am not sure which line could be causing the error, but one thing I know is that the error is always triggered when I push the elements from the panel that prints out the mx:Repeater elements.
One question I have is, who is the caller it is referring to? Since I have various states, (each different checkbox triggered results in a different state. For example, here is an example from livedocs: http://livedocs.adobe.com/flex/201/html/wwhelp/wwhimpl/common/html/wwhelp.htm?context=Live Docs_Book_Parts&file=states_039_03.html. How can I use viewStack here instead?
If you compile a debug build and view it in a debug player, the line numbers for the stack trace will be displayed.
You can also step through the code in the debugger until the error happens. You will know where it is then.
Finally, you can add trace statements that will tell you where the error is.
Just make each container that has the repeaters in it be a child of the ViewStack.
Hmm, also, I do not think it is a good idea to try to switch repeater in a state. Wrap it in a container and shwitch the container using the states. But use ViewStack, it is much cleaner and will give you fewer problems.
I'm having this problem as well.. with a repeater and a radio button.
But the stack trace doesn't help me much...
I can't figure out how to step through this code because if I open up the SysteManager.as in the flex source, I can't put breakpoints on it.
the error occurs when I click on a radio button. I have a change event on the radiobuttongroup but it isn't called. I do not have a mousedown event specified.
Here's the whole MXML file...
frak, never mind. my problem was that the MXML file above was *NOT* the main application file, and I had an mx:application tag inside an mx:application tag, and apaprently that caused some confusion on the part of Flex.