Hey, you know what would make this a lot easier? A new property called objectVersion (a number), and a stack property called stackObjects (an array). Each time an object is edited, the objectVersion gets incremented by 1. This way you could simply compare a list of stackObjects with a saved one, and a list of objectVersions with a saved one of that.
Why you say? Why not just loop through all objects in a stack? It's been discussed before and things like Datagrids really throw a wrench in the works. I suppose that would be true of any approach, but these properties could treat all the objects in a Datagrid group as a single object, and not list the individual components. The same could be done with things like background groups. Even further, a new message called stackUpdate could be sent each time a stack is saved that had objects which were edited, which could be handled to send updates to another developer working on the same stack. Or maybe I am dreaming I dunno. Bob On Jun 7, 2012, at 11:37 AM, Peter Haworth wrote: > I think I brought this up the last time this discussion surfaced, but I > think there's benefit to be had from being to able to discern exactly what > changes took place between two versions of a stack file - were any controls > added/deleted or did their properties change, which scripts were > added/deleted/changed, etc > > I started on a project to implement this but haven't had an opportunity to > get back to it. Theoretically, the information I store could be used to > recreate a stack but that wasn't my intention and I suspect that it would > be full of pitfalls. > > Pete > lcSQL Software <http://www.lcsql.com> _______________________________________________ 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
