> > Brian M. wrote: > > One other thing that could be done is to extend the export to include > > everything that the engine knows about the widget (i.e. add the > > properties array to it). > > The widget author can already do that by defining a list of persistent > properties. Why should the engine override that?
I see this as a unification rather than override. When a stack is saved it asks each widget what it wants to save but also includes other properties too (rect, layer, id, ...). _______________________________________________ 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
