|
Since this is an urgent problem, how about working with what you do
have: The onwidth lets you know that the width changed. From there you can set a timer (see the reference for LzTimer) to write a your cookie, and a flag to let you know that you've set the timer. When the timer fires, check the actual width and write your cookie, and clear the flag. Any more onwidth events while the flag is set can be ignored, so you don't kill performance trying to write the cookie on every onwidth. It's not a pretty way to do it, but it will get the job done (except in the small case where the user closes the application before the timer has a chance to fire, but assuming you set the timer for a reasonable time like 1 second, this isn't that big a hole). I hope that helps. Jim Grandy wrote:
-- Jason Stafford Principal Developer Inspiration Software, Inc. The leader in visual thinking & learning Introducing INSPIRATION(r) 8, the essential tool to visualize, think, organize and learn. Students use Inspiration to plan, research and complete projects successfully. Learn more at www.inspiration.com. 503-297-3004 Extension 119 503-297-4676 (Fax) 9400 SW Beaverton-Hillsdale Highway Suite 300 Beaverton, OR 97005-3300 |
_______________________________________________ Laszlo-dev mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
