The interesting question about that is now: What is in memory after [1] save? [2] save as? [3] save copy as (not yet implemented)?
If I'm correct then it is ALWAYS the same, NOTHING is changed in memory. Only with [2] the file on disk is changed to which the object in memory links (and which is used for the next save or revert command). So we can use save and one or both of [2] or [3]. This yields of course different backup methods, but your work goes on in any case with an unchanged object in memory. -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Windows-Equivalents-for-Shell-cp-copy-tp4706590p4706660.html Sent from the Revolution - User mailing list archive at Nabble.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
