Using States within a non-optimized Module.

[charlesshoults]

I have a project in which I have fourteen modules tied to the main application. When a module is created, it provides options for Optimizing the module to the application. Up to this point, I've said yes to each of these. This has been working fairly well. The parent application has 42 states and some of the modules have up to 13 of their own. Everything coexists and works well. In a module, I can say currentState="Mailer" and it changes to reflect the state of that module without affecting the parent application.

This weekend, I created a new module and told it not to Optimize against the parent application, testing to see how it affects swf file sizes. The module has 7 states, but when clicking on a button, nothing happens. If I put mx.controls.Alert.show(String(currentState)); , it correctly gives me an alert for the state I'm telling it to go to but the display stays on it's initial state. I'm guessing that the state change is actually taking place but somehow, the module is not refreshing the display but am not quite sure how to solve it.

:confused: Can anyone help in this?

[charlesshoults]

Actually, as I began to strip bits of code out of the module, I've discovered that it's something within my code that is preventing the refresh. I'll have to play with it tonight and get the bugs out.