puremvc
|
|
« Reply #1 on: April 07, 2010, 08:01:45 » |
|
I don't see anything in particular wrong with this, certainly nothing that would seize up text box.
You mention using a code-behind structure. This isn't a recommended practice with PureMVC. How are you implementing it? Is it in the form of Mediators that know everything about the internal structure of their components and puppeteer them? Could it be an action that one of these Mediators takes?
BTW, if you're using Flex, you should try using the debugger to set breakpoints and follow the thread of execution. IMHO, trace statements are a stone age approach to debugging.
-=Cliff>
|