more rev 3.0 woes - losing the will to live

[Mark Schonewille]

Hi Bernard,

I'm sorry to read that you have more problems. Apparently, you save  
the stacks one more time, somehow.

Make sure that your scripts don't save the stacks again, when quitting  
Rev 3.0, or set the Rev preferences to preserve the (legacy) format,  
or don't click "Save" when Rev asks you whether or not to save the  
stack.

I go back and forth between different versions all the time and never  
see this problem, although I admit I have to be really careful that I  
don't accidentally save a stack in the wrong format. Is there anything  
else that might be relevant to reproduce the problem?

I guess you could save a stack and copy it to a different place before  
quitting Rev 3.0, even though this wouldn't be a very elegant solution.

--
Best regards,

Mark Schonewille

Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz
Dutch forum: http://runrev.info/rrforum/

Benefit from our inexpensive hosting services. See http://economy-x-talk.com/server.html 
  for more info.

On 6 okt 2008, at 13:45, Bernard Devlin wrote:

> Since I've now had to revert to using Rev 2.6.1 from 3 years ago, I  
> need to
> convert various stacks to 'legacy format'.  After doing this with  
> some of
> stacks, I then found that they were still in a post 2.7 format.  I  
> thought
> I'd made a mistake and went over it many times using Rev 3.0 and  
> 2.6.1, but
> the stacks simply wouldn't convert.  I was reduced to examining the  
> stacks
> in a text editor to see that they did indeed say 2.4, but then as  
> soon as I
> quit Rev 3.0 they would not load in 2.6.1, and looking at them again  
> in a
> text editor, they were back in 2.7 formt.  But yesterday I was able  
> to save
> my performance test stack in legacy format (maybe it was written on  
> 2.6.1
> though, I can't remember).  I just opened it in 3.0, and saved it in  
> 2.6.1
> as legacy and it remained as legacy after rev 3.0 quit.
>
> But here's what I'm seeing with some stacks:
>
> [user at localhost ~]$ ls *.rev
> perf-test-leg.rev test-legacy.rev
> [user at localhost ~]$ more test-legacy.rev
> #!/bin/sh
> # MetaCard 2.4 stack
> # The following is not ASCII text,
> # so now would be a good time to q out of more^L
> [user at localhost ~]$ more test-legacy.rev
>      <<<---- REV 3.0 was quit just before this point
> REVO2700�revNavigator 1 �R��global
> gScriptBuddyIDarray,gScriptBuddyLineArray,gSB
> UpdateSelection,gSBLeadSpaces
>
> I had thought maybe it was because these stacks were in the plugins  
> folder
> of 2.6.1 that they were being reverted on exit from 3.0.  But then I  
> saved
> one of them to my home directory, and checked it was in 2.4 format.   
> But as
> soon as I quit Rev 3.0 it was back in 2.7 format (as you can see  
> above).  At
> no point did Rev 3.0 ask me if wanted to save the stacks when I  
> chose to
> quit, so I can see no reason why they are back in 2.7 format.   I  
> tried it
> on 2.9, and it too re-converted the stack on quitting.
>
> Could someone else please confirm this apparently erratic  
> behaviour.  I'm
> starting to doubt my sanity.  The particular stacks were the  
> stsmlxEditor
> and Geoff Canyon's revNavigator.  Maybe it is only a Linux thing.
>
> I just want to know that saving in legacy format is still working  
> reliably.
> I have a lot more of my own stacks to convert, and if this doesn't  
> work,
> I'm stuck with the insanely buggy 3.0 (I have no confidence in 2.9  
> either -
> it locked up my laptop yesterday requiring a hard reset).
>
> Bernard