This is the same type of problem as deleting an object from a user interaction with the object - but more common use case and I don;t know a good way of doing that either. I use:
send "delete_Object" to somewhere in 2 ticks But it is messy and tends to be a bit unreliable in my experience. I don't know a way around it other than avoiding any events being trapped within the object itself - but that is not so easy. On Sat, 15 Jul 2023 at 20:47, Dick Kriesel via use-livecode < use-livecode@lists.runrev.com> wrote: > > > On Jul 15, 2023, at 8:06 AM, Paul Dupuis via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > So in the instances where you have a script that creates an object and > then sets the script of that object (example below), what is you best > practice for having the script in a script and still be readable? > > Hi, Paul. The best way to set the script may be not to; that is, instead > set the new object’s behavior to a button that contains the readable script. > — Dick > _______________________________________________ > 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