I have a property editor that builds/positions its editing controls dynamically, based on some simple rules. When a new object is selected, the editing controls for the recent object are removed and replaced with editing controls for the newly selected object. Using this process, I don't have to lay out hardwired screens for every existing or future control that might come along. Depending on how long the editing session is, the editor could go wind up creating and deleting hundreds or even thousands of controls. So in this case, many objects are created that are not intended to be saved.
Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 9/23/15, 10:27 AM, "use-livecode on behalf of Richard Gaskin" <[email protected] on behalf of [email protected]> wrote: >The "how" was pretty clear from the Release Notes. I just couldn't >figure out the "why". How often to people create objects they don't want? > >For ID preservation I tend to do what the DG does, hiding rather than >disposing of controls I'm likely to need again. _______________________________________________ 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
