Me too--in my case I get it right when my application loads (and the opening screen is very simple, just a control bar and a viewstack with a panel in it). It's intermittent, too; seems to go away for a while after restarts, but inevitably comes back again. This definitely started showing up with 2.0.1.
- Chris --- In [email protected], Shannon Hicks <[EMAIL PROTECTED]> wrote: > > I have this problem, but only on one computer out of 4. It happens when, > on that computer, I have more than one Flex app open at a time. It > doesn't matter if I run the debugging plugin or the production plugin, I > have the same problem. The production plugin, of course, doesn't throw > an error, but it stalls at the same point, so I have to assume it's the > same error. > > Shan > > Mikey wrote: > > > > Howdy all, > > > > Sorry to start my first/second post off on a bad note but it's warrented. > > > > Let's start with the error: > > *ArgumentError: Error #2082: Connect failed because the object is > > already connected. > > at flash.net::LocalConnection/connect() > > at mx.managers::HistoryManagerImpl$iinit() > > at mx.managers::HistoryManagerImpl$/getInstance() > > at mx.core::Singleton$/getInstance() > > at mx.managers::HistoryManager$/get ::impl() > > at mx.managers::HistoryManager$/register() > > at mx.containers::Accordion/::addedHandler() > > at flash.display::DisplayObjectContainer/addChildAt() > > at > > mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::$addChildAt() > > at mx.core::Container/addChildAt() > > at mx.core::Container/addChild() > > at mx.core::Container/createComponentFromDescriptor() > > at mx.core::Container/createComponentsFromDescriptors() > > at mx.core::Container/mx.core:Container::createChildren() > > at mx.core::UIComponent/initialize() > > at mx.core::Container/initialize() > > at mvc.view::LeftMenuView/initialize() > > at > > mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::childAdded() > > at > > mx.core::Container/http://www.adobe.com/2006/flex/mx/internal::childAdded() > > at mx.core::Container/addChildAt() > > at mx.core::Container/addChild() > > at mx.core::Container/createComponentFromDescriptor() > > at mx.core::Container/createComponentsFromDescriptors() > > at mx.core::Container/mx.core:Container::createChildren() > > at mx.core::UIComponent/initialize() > > at mx.core::Container/initialize() > > at > > mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::childAdded() > > at > > mx.core::Container/http://www.adobe.com/2006/flex/mx/internal::childAdded() > > at mx.core::Container/addChildAt() > > at mx.core::Container/addChild() > > at mx.core::Container/createComponentFromDescriptor() > > at mx.core::Container/createComponentsFromDescriptors() > > at mx.containers::ViewStack/::instantiateSelectedChild() > > at mx.containers::ViewStack/mx.containers:ViewStack::commitProperties() > > at mx.core::UIComponent/validateProperties() > > at mx.managers::LayoutManager/::validateProperties() > > at mx.managers::LayoutManager/::doPhasedInstantiation() > > at Function/http://adobe.com/AS3/2006/builtin::apply() > > at mx.core::UIComponent/::callLaterDispatcher2() > > at mx.core::UIComponent/::callLaterDispatcher()* > > -------------------------------------------------------- > > > > I've looked this error up at Adobe with no further info. It happens > > when an accordian/tab manager gets ctrated. It's happened a few times > > on a few different projects. It's obviously something I'm doing (which > > is hard to grasp as I like all of you write perfect code) as it > > happens when I've added a fair amount of code. I figuerd it was a bug > > but now I'm using 2.0.1 so no go. > > > > Any ideas? Maybe even some pointless mildly amusing rambling to make > > me feel better would be good. > > > > >
