Re: [flexcoders] Re: Serious Bug in HistoryManager (introduced in latest release?)

2007-02-07 Thread Bjorn Schultheiss
Yo Z, Each Manager is registered as a singleton. code excerpt; Singleton.registerClass(mx.managers::ICursorManager, Class (getDefinitionByName(mx.managers::CursorManagerImpl))); Singleton.registerClass(mx.managers::IDragManager, Class

Re: [flexcoders] Re: Serious Bug in HistoryManager (introduced in latest release?)

2007-02-07 Thread Michael Schmalle
Oh yeah one more thing. I know why they did this. At least a perspective. If you have version 2.0 linking in ManagerA and they change the implementation to ManagerB in 2.5, ManagerA will not be linked in unless ManagerA is linked, other wise ManagerB is linked in, in 2.5 and the string

Re: [flexcoders] Re: Serious Bug in HistoryManager (introduced in latest release?)

2007-02-07 Thread Michael Schmalle
Hey, Don't get me wrong here but, what happens when you use getClassDefinition() and you didn't link in your class as a static dependency? Same error as you get here. Is it a flaw or a chicken and egg thing like 'my computer can't entirely think for me' thing. Peace, Mike On 2/7/07, Bjorn

Re: [flexcoders] Re: Serious Bug in HistoryManager (introduced in latest release?)

2007-02-05 Thread Bjorn Schultheiss
Here's a reply i got from one of the engineers, Alex Harai on what could be a related issue. This error occurs for two reasons: One is that somehow, the DragManager or DragManagerImpl is not linked into the movie. The other, and more common reason is that more than one module is using