more rev 3.0 woes - losing the will to live

[Joe Lewis Wilkins]

Hi Bernard, and others

I have not followed this thread closely, so I may be way off base;  
however, I
believe that you are using Rev on a variety of Unix flavors - true?

Be that the case, since I think that few Rev developers/users are  
using Unix,
it would be a big help if you were to indicate that you ARE.  
Particularly when
you are having such difficulties. Otherwise, it is kind of scary to  
the rest of us.
I'm even thinking that it might not be a totally bad idea to have  
different lists
for the different platforms? I realize that a problem on one could  
also be one
on the others as well, but???? This might not be a bad option. Anyone?

I've been using 3.0 pretty much since it first came out - Mac OSX -  
and have
not had any appreciable problems. Also saving as Legacy. A couple of  
kinks
there, but probably associated with my not knowing the Legacy  
limitations well.

So, my request is that maybe we can all better identify our platforms,  
particularly
when airing complaints, so we may look at the things that most effect  
what we
are doing.

TIA

Joe Wilkins

On Oct 6, 2008, at 9:54 AM, Bernard Devlin wrote:

> Eric and Mark, Thanks for your attempts to save my sanity (of  
> course, it
> could well be too late).
>
> I re-started 3.0, loaded stsMLXEditor, found the first guilty- 
> looking 'save
> this stack', and commented it out... and then 3.0 crashed before I  
> could
> even save it!  Unbelievable.  I couldn't face going through every  
> stack and
> finding every handler that caused a stack to be saved.
>
> What I didn't understand is that I have checked 'preserve stack file  
> version
> on stacks saved in legacy format' in Rev's preferences.  Yet it  
> seemed to be
> ignoring that in these stacks that have several of their own self- 
> saving
> events.  After searching bugzilla I found that it this is indeed  
> broken:
> http://quality.runrev.com/qacenter/show_bug.cgi?id=4695.  Ken Ray  
> provides a
> workaround for it: in the MB type: "set the stackFileversion to  
> 2.4;save
> this stack".  After doing that and quitting Rev, the stack is  
> finally in 2.4
> and remaining in 2.4.
>
> Thanks for your commiserations.  I know I must sound like my whining  
> button
> is stuck on 'loop', but these have been the worst 5 months I've had  
> with Rev
> in 7 years.