Hi Richard,
In this case, it would make sense to use separate files. I bet users who
are in one jurisdiction don't want to load all the stacks for all other
jurisdictions into memory. So, make the stacks separate files and load
only the required files into memory. That will allow you to track the
change dates of each file individually.
--
Mark Schonewille
http://economy-x-talk.com
Buy the most extensive book on the
LiveCode language:
http://livecodebeginner.economy-x-talk.com
Op 9/19/2015 om 18:13 schreef Dr. Hawkins:
Is there a practical way to automatically track the change dates for
substacks?
I'm about to end up with something like 100 of them (one for each judicial
district)
At the moment, I have routines that step through all of my cards every time
I bump the revision, but it would be nice to be able to skip stacks.
I guess I'm looking for something like a last changed date on a directory,
but for substacks instead.
_______________________________________________
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
