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 Sch

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 decouples

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 (getDefinitionByName("mx.managers::Dra

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

2007-02-07 Thread zenwarden
I can't test the fix because I cannot replicate the bug. It has mysteriously vanished...The next time I see it, I will try the suggested fix and report back. Also sorry if I ranted in my last post. Just don't like to see any problems with my new favorite technology. --- In flexcoders@yahoogroup

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

2007-02-06 Thread zenwarden
I will give it a try. One question and one comment: Question: Did you actually mean drag manager or did you mean History manager? (I'll try both sperately). Commnet: I've been a virtual evenagilist for flex at the company I work for; I am very impressed with product and love using it. But this d

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 t

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

2007-02-05 Thread zenwarden
I am seeing this mostly when I run unit test using the flexunit.swf. And I am consistantly seeing it in that situation I do occasionaly see it when running a single-swf app through the builder (However it is making a connection to a server when it occurs). Chris W --- In flexcoders@yahoogroups

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

2007-02-05 Thread Chris Luebcke
Sorry Bjorn, I should note: I was experiencing this problem when my app was a single monolithic SWF. When I started breaking it into modules, I started getting the exception when the first module loaded. But it was always intermittent in my case, although I think it's been constant for others. ---

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

2007-02-05 Thread Chris Luebcke
The only known workaround is to not use the history manager. I keep bumping this on the Adobe forums, to no avail: http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=60&catid=585&threadid=1238955&enterthread=y (The subheading is, "Appears to be related to history manager - Flex