question of practise

Jim Bufalini jim at visitrieve.com
Tue Mar 10 15:46:45 EDT 2009


Hi Peter,

Yes. So what I meant to communicate in my original misunderstood answer is
that Changed Code Picker handles all of this for you and a lot more.

Aloha from Hawaii,

Jim Bufalini

> -----Original Message-----
> From: use-revolution-bounces at lists.runrev.com [mailto:use-revolution-
> bounces at lists.runrev.com] On Behalf Of Peter Brigham MD
> Sent: Tuesday, March 10, 2009 7:05 AM
> To: use-revolution at lists.runrev.com
> Subject: RE: question of practise
> 
> Ah. Thanks for the clarification. Not a one-click solution, then, but
> definitely a help. I have a couple of stack systems that I use, one
> derived from the other, each a little different, and up to now I have
> been closing one (with destroystack = true) and opening the other,
> when I want to copy some scripts from one to the other. Ultimately I
> need to change the stack names to unique titles -- and all the
> references to them in the scripts -- so I can keep both stack files in
> memory at once when I need to. I will check out Eric's utility.
> 
> Peter M. Brigham
> pmbrig at gmail.com
> 
> On Mon, 9 Mar 2009 10:32:18, "Jim Bufalini" <jim at visitrieve.com> wrote:
> 
> > Hi Peter,
> >
> > No, you misunderstood, probably because I was unclear. If Changed
> Code
> > Picker actually changed stacks, it would be a PITA for everyone. ;-)
> >
> > In order for Changed Code Picker to work, it clones the reference
> > stack
> > (Stack 1) and renames the clone in memory only. Nothing is changed
> > to disk.
> > This then allows the stack you want to compare to and change (Stack
> > 2) to be
> > loaded into memory (actually this stack is cloned and renamed also,
> > but only
> > in memory). Changed Code Picker makes no changes to your actual
> > stacks on
> > disk, either Stack 1 or Stack 2. But this allows comparing two
> > versions of
> > identically named stacks.
> >
> > Only you can change Stack 2 by requesting it be sent to your editor
> > (either
> > the Rev editor or GLX2) and manually making a change and manually
> > saving
> > from your editor. In this case, the actual stack (Stack 2) is loaded
> > into
> > your editor and is saved under whatever it was originally named and
> > is the
> > same as if you loaded only that stack, edited it, and saved it.
> >
> > Aloha from Hawaii,
> >
> > Jim Bufalini
> >
> >> Does this mean that Changed Code Picker handles changing all the
> >> references to the stack names in all the scripts? That's the real
> >> PITA, for me.
> >>
> >> Peter M. Brigham
> >> pmbrig at gmail.com
> >
> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution




More information about the use-livecode mailing list