question of practise

[Jim Bufalini]

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



> -----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: Monday, March 09, 2009 10:04 AM
> To: use-revolution at lists.runrev.com
> Subject: E: question of practise
> 
> 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
> 
> 
> On 8 Mar 2009 04:02:56, "Jim Bufalini" <jim at visitrieve.com> wrote:
> 
> >
> >> Jacqueline and Everyone,
> >>
> >> Just use Eric Chatonet's Changed Code Picker.
> >> http://www.sosmartsoftware.com/?r=revolution&l=en. Fourth one down.
> >> It
> >> automatically handles all the renaming of stacks AND their
> >> substacks and
> >> parses everything down to the handler level (which you can uncheck
> >> if you've
> >> handled it and/or otherwise don't want to see it anymore, and it's
> >> FREE! (my
> >> comment about tips aside ;-)
> >>
> >> It works well with the Rev editor and GLX2. I use it all the time
> >> (Eric did
> >> too, that's why he wrote it) and it's a life saver, especially when
> >> you are
> >> working with old code (maybe you just wrote it last month ((or last
> >> week?)),
> >> but something that you don't exactly remember why you did it that
> >> way and
> >> only remember after you change it - or is that just me? ;-) that
> >> you are
> >> updating and mess up.
> >>
> >> 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 Tiemo Hollmann TB
> >>> Sent: Saturday, March 07, 2009 10:52 PM
> >>> To: 'How to use Revolution'
> >>> Subject: AW: question of practise
> >>>
> >>> Hi Jacqueline,
> >>> yeah, that's how I helped me now, but as Mark says, with multiple
> >>> stacks /
> >>> substacks it's a hassle
> >>> Tiemo
> >>>
> >>>> -----Ursprüngliche Nachricht-----
> >>>> Von: use-revolution-bounces at lists.runrev.com [mailto:use-
> >>>> revolution-
> >>>> bounces at lists.runrev.com] Im Auftrag von Mark Wieder
> >>>> Gesendet: Samstag, 7. März 2009 21:12
> >>>> An: use-revolution at lists.runrev.com
> >>>> Betreff: Re: question of practise
> >>>>
> >>>> Jacque-
> >>>>
> >>>> Saturday, March 7, 2009, 9:07:22 AM, you wrote:
> >>>>
> >>>>> It's easy. Open the first stack and rename it temporarily, for
> >>> example:
> >>>>
> >>>> Not that easy if the stack has substacks. And a real pita if there
> >>> are
> >>>> multiple substacks to rename.
> >>>>
> >>>> --
> >>>> -Mark Wieder
> >>>> mwieder at ahsoftware.net
> >>>
> >
> _______________________________________________
> 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