[flexcoders] Re: RangeError: Error #2006 using menu !
the 2.01 update does not seems to correct this bug... --- In flexcoders@yahoogroups.com, "Deepa Subramaniam" <[EMAIL PROTECTED]> wrote: > > Hello - > > > > We fixed a few bugs where this was happening in Menu and MenuBar. We were not correctly adding and removing the child menu instances to the SystemManager and eventually the indices would get out of sync and you'd RTE. > > > > These have been fixed since the Flex 2 build went out and will be included in the next drop of Flex which will be out soon. > > > > Deepa > > Flex SDK > > > > > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of droopyflex > Sent: Tuesday, November 07, 2006 12:50 AM > To: flexcoders@yahoogroups.com > Subject: [flexcoders] Re: RangeError: Error #2006 using menu ! > > > > --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> , "Ciarán" wrote: > > > > Hi, > > > > I found this difficult to reproduce. I'm a bit of a flex rookie, but > > given the exception I think flex is complaining after it's looked for > > something and not found it because it hasn't been initialized (yet). > > To my understanding, creationComplete is dispatched after > > initialization of components. I haven't yet experienced the error > > since I changed: > > > > creationComplete="initCollections();" > > > > to > > > > initialize="initCollections()" > > > > But since it's hard to reproduce I can't tell for sure if this is at > > all related to anything happening here... > > the bug is not related to this. even the MenuBar is properly filled by > initCollections(), there is something wrong in MenuBar::showMenu() > > After many tries, here a way to reproduce it: > - build the menubar post in this Thread. (taken from Menubar doc) > - click on "Menu 2" > - now the tricky part: move to "Menu Item 2-B" but immediatly go to > "Menu 1" then immediatly go to "Menu 2" before "Menu Item 2-B" open > and before "Menu 1" open (may be). > - "Menu Item 2-B" should open when "Menu 2" is closed, or something > like that > - MenuBar::showMenu() should crash on "Menu 2" > > this is not easy to reproduce, may be because the submenu is not big. > BUT: playing with big menu with big submenu for a moment always crash. >
[flexcoders] Re: RangeError: Error #2006 using menu !
the bug still remain in 2.0.1 update ! --- In flexcoders@yahoogroups.com, "Deepa Subramaniam" <[EMAIL PROTECTED]> wrote: > > Hello - > > > > We fixed a few bugs where this was happening in Menu and MenuBar. We were not correctly adding and removing the child menu instances to the SystemManager and eventually the indices would get out of sync and you'd RTE. > > > > These have been fixed since the Flex 2 build went out and will be included in the next drop of Flex which will be out soon. > > > > Deepa > > Flex SDK > > > > > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of droopyflex > Sent: Tuesday, November 07, 2006 12:50 AM > To: flexcoders@yahoogroups.com > Subject: [flexcoders] Re: RangeError: Error #2006 using menu ! > > > > --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> , "Ciarán" wrote: > > > > Hi, > > > > I found this difficult to reproduce. I'm a bit of a flex rookie, but > > given the exception I think flex is complaining after it's looked for > > something and not found it because it hasn't been initialized (yet). > > To my understanding, creationComplete is dispatched after > > initialization of components. I haven't yet experienced the error > > since I changed: > > > > creationComplete="initCollections();" > > > > to > > > > initialize="initCollections()" > > > > But since it's hard to reproduce I can't tell for sure if this is at > > all related to anything happening here... > > the bug is not related to this. even the MenuBar is properly filled by > initCollections(), there is something wrong in MenuBar::showMenu() > > After many tries, here a way to reproduce it: > - build the menubar post in this Thread. (taken from Menubar doc) > - click on "Menu 2" > - now the tricky part: move to "Menu Item 2-B" but immediatly go to > "Menu 1" then immediatly go to "Menu 2" before "Menu Item 2-B" open > and before "Menu 1" open (may be). > - "Menu Item 2-B" should open when "Menu 2" is closed, or something > like that > - MenuBar::showMenu() should crash on "Menu 2" > > this is not easy to reproduce, may be because the submenu is not big. > BUT: playing with big menu with big submenu for a moment always crash. >
RE: [flexcoders] Re: RangeError: Error #2006 using menu !
Hello – We fixed a few bugs where this was happening in Menu and MenuBar. We were not correctly adding and removing the child menu instances to the SystemManager and eventually the indices would get out of sync and you’d RTE. These have been fixed since the Flex 2 build went out and will be included in the next drop of Flex which will be out soon. Deepa Flex SDK From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of droopyflex Sent: Tuesday, November 07, 2006 12:50 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: RangeError: Error #2006 using menu ! --- In [EMAIL PROTECTED]ups.com, "Ciarán" <[EMAIL PROTECTED]..> wrote: > > Hi, > > I found this difficult to reproduce. I'm a bit of a flex rookie, but > given the exception I think flex is complaining after it's looked for > something and not found it because it hasn't been initialized (yet). > To my understanding, creationComplete is dispatched after > initialization of components. I haven't yet experienced the error > since I changed: > > creationComplete="initCollections();" > > to > > initialize="initCollections()" > > But since it's hard to reproduce I can't tell for sure if this is at > all related to anything happening here... the bug is not related to this. even the MenuBar is properly filled by initCollections(), there is something wrong in MenuBar::showMenu() After many tries, here a way to reproduce it: - build the menubar post in this Thread. (taken from Menubar doc) - click on "Menu 2" - now the tricky part: move to "Menu Item 2-B" but immediatly go to "Menu 1" then immediatly go to "Menu 2" before "Menu Item 2-B" open and before "Menu 1" open (may be). - "Menu Item 2-B" should open when "Menu 2" is closed, or something like that - MenuBar::showMenu() should crash on "Menu 2" this is not easy to reproduce, may be because the submenu is not big. BUT: playing with big menu with big submenu for a moment always crash. __._,_.___ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com SPONSORED LINKS Software development tool Software development Software development services Home design software Software development company Your email settings: Individual Email|Traditional Change settings via the Web (Yahoo! ID required) Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe __,_._,___
[flexcoders] Re: RangeError: Error #2006 using menu !
--- In flexcoders@yahoogroups.com, "Ciarán" <[EMAIL PROTECTED]> wrote: > > Hi, > > I found this difficult to reproduce. I'm a bit of a flex rookie, but > given the exception I think flex is complaining after it's looked for > something and not found it because it hasn't been initialized (yet). > To my understanding, creationComplete is dispatched after > initialization of components. I haven't yet experienced the error > since I changed: > > creationComplete="initCollections();" > > to > > initialize="initCollections()" > > But since it's hard to reproduce I can't tell for sure if this is at > all related to anything happening here... the bug is not related to this. even the MenuBar is properly filled by initCollections(), there is something wrong in MenuBar::showMenu() After many tries, here a way to reproduce it: - build the menubar post in this Thread. (taken from Menubar doc) - click on "Menu 2" - now the tricky part: move to "Menu Item 2-B" but immediatly go to "Menu 1" then immediatly go to "Menu 2" before "Menu Item 2-B" open and before "Menu 1" open (may be). - "Menu Item 2-B" should open when "Menu 2" is closed, or something like that - MenuBar::showMenu() should crash on "Menu 2" this is not easy to reproduce, may be because the submenu is not big. BUT: playing with big menu with big submenu for a moment always crash. -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/flexcoders/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
