I’m not sure I follow. The proposal I’m making is no different than what the engine does today, just allowing the same information to be saved to an array. The internal state of the widget is the same as what would be used on export/import. It just adds the other properties (rect, ...) to the array.
I’ll need to look again, but I think that export uses OnSave to get the array. Import uses OnLoad. This would save the step of setting the other properties. On Sun, Feb 25, 2018 at 10:02 PM hh via use-livecode < email@example.com> wrote: > > Brian M. wrote: > > My 0.02 is that export should mirror what the engine saves to the stack > > file such that import could exactly recreate an object (with some logic > on > > how to handle ID collisions - overwrite, throw error, assign new ID...) > > If you are developing and testing a widget this would make you crazy. > What I want are some persistent properties from "OnSave" and "OnLoad" but > NOT the saved state of a probable buggy widget. > > And if I open a stack half a year later while the widget was updated, > then I want, as it is currently, the new version without deleting and > reinstalling all widgets of that kind (think of a stack that has a lot of > svg-icon-widgets). > > > _______________________________________________ > use-livecode mailing list > firstname.lastname@example.org > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list email@example.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode