In the LC 8 Release Notes I see: Objects are only deleted on idle (8.0.0-dp-3) The engine will now flush any recently deleted objects after each command as long as they were created during the current event handling loop. If an object is created during one event handling loop, and then deleted during another nested event handling loop it won't be flushed until control returns to the original event handling loop. The upshot is that in tight loops, creating and deleting objects will result in objects being flushed immediately, reducing memory usage and making it easier to write object processing code which creates and deleted many objects
I'm having a hard time conceiving of a circumstance in which it's necessary o build a large number of objects only to delete them again in the same handler.
What am I missing? -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ____________________________________________________________________ [email protected] http://www.FourthWorld.com _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
