This content has been marked as final. Show 2 replies
No guarantees that I can help, but first check this thread on flexcoders if you haven't already:
And this relevant quote, which apparently originated from an unnamed engineer at Adobe. Here he's/she's suggesting that this problem can occur when a manager class is loaded by a module instead of the top-level application; when this happens, other modules (or the application) see that the class has already been loaded, but are unable to instantiate it because the class definition exists in the module it was first referenced in, which is not visible to the other modules or application. Or something like that; it's still a bit foggy to me.
The simple solution is to link the DragManager into the main application by putting something like this in a script block [in the main application]
import mx.managers. DragManager;
This fattens your application a little. More complex solutions involve loading the DragManager into the main application' s application domain.
Obviously this is about DragManager, not HistoryManager, but the conversation (though it started with HistoryManager) became about managers in general.
Anyway, here's hoping that helps a little,
Thanks for your reply.
I put the following at the top of my app and repeated module unloading and loading work without errors:
private var hm:HistoryManager;