I agree, mostly. I tend to use it if I'm altering stuff on stage that might bog down memory on slower machines, because it seems that slower machines sometimes have trouble compositing the stage correctly in low memory situations unless an updateStage() is forced.
Charlie Fiskeaux II Media Designer The Creative Group www.cre8tivegroup.com 859/858-9054x29 cell: 859/608-9194 ----- Original Message ----- From: "Kevin McFarland" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, June 19, 2003 12:25 PM Subject: <lingo-l> re: editable of member > <<Sometimes updateStage() helps, even if it shouldn't be needed.>> > > It's over-used. Whenever I come across code with updateStage commands sprinkled liberally throughout, I become less sure that the author really understood how director works (event messaging, hierarchy etc). > > Now having said that, yes, every once in a blue moon there might be those oddball situations where it helps. But in general, IMO it's oftentimes used as a hedge for ignorance. > [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!] > [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
