The other consideration is that the loop is likely going so fast that even with the "wait 0" line the screen update may be too slow to keep up and the only thing you'll get will be the final number.
-- Peter Peter M. Brigham pmb...@gmail.com http://home.comcast.net/~pmbrig On Sep 11, 2012, at 9:04 AM, Richard Gaskin wrote: > Gabriel Johnson wrote: >> I am having an issue getting output to display during a loop. I've >> tried lock/unlock screen but unlock screen does not seem to cause the >> screen to update. The only thing that works is "wait 0 seconds" but >> this causes bizarre behavior in some cases (mouseDown/mouseUp not >> behaving correctly [even when I use wait "with messages"]). > > It works well without the "with messages" clause, so just adding "wait 0" > should do what you need. > > That said, it appears that very soon that particular bit of arcane knowledge > will no longer be needed to have text displayed reliably - members of the Dev > Program can read Mark Waddingham's thoughtful comments on this here, noting > that going forward the update behavior will be made more consistent across > platforms: > > <http://quality.runrev.com/show_bug.cgi?id=10333> > > Until that version is released, simply adding "wait 0" will do what you need. > > -- > Richard Gaskin > Fourth World > LiveCode training and consulting: http://www.fourthworld.com > Webzine for LiveCode developers: http://www.LiveCodeJournal.com > Follow me on Twitter: http://twitter.com/FourthWorldSys > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode