Re: Stack file format change in 2.7 - BACK UP!

2006-04-21 Thread David Burgun
Thanks a lot! All the Best Dave On 21 Apr 2006, at 13:51, Pierre Sahores wrote: This info is from Guy Petinon (french rev list) : Pour changer la version d'une pile: ouvri "message boxe" et taper "set the stackfileversion to 2.5" par exemple à partir de la version 2.7 To change the stack's

Re: Stack file format change in 2.7 - BACK UP!

2006-04-21 Thread Pierre Sahores
This info is from Guy Petinon (french rev list) : Pour changer la version d'une pile: ouvri "message boxe" et taper "set the stackfileversion to 2.5" par exemple à partir de la version 2.7 To change the stack's version from 2.7 to (as an example) to 2.5 : just type "set the stackfileversion t

Re: Stack file format change in 2.7 - BACK UP!

2006-04-21 Thread David Burgun
I hope so! That's great! All the Best Dave On 20 Apr 2006, at 14:36, Geoff Canyon wrote: I think saving in the pre-2.7 format is available in the upcoming release. gc On Apr 20, 2006, at 2:41 AM, David Burgun wrote: Hi All, I really can't understand all the mystery surrounding this "fix

Re: Stack file format change in 2.7 - BACK UP!

2006-04-20 Thread J. Landman Gay
David Burgun wrote: I really can't understand all the mystery surrounding this "fix" to allow backwards compatibility. The beta testers know about it (if you purchase Enterprise, you are automatically on that list,) but the details were pulled from the final release for a number of reasons

Re: Stack file format change in 2.7 - BACK UP!

2006-04-20 Thread Geoff Canyon
I think saving in the pre-2.7 format is available in the upcoming release. gc On Apr 20, 2006, at 2:41 AM, David Burgun wrote: Hi All, I really can't understand all the mystery surrounding this "fix" to allow backwards compatibility. As far as I understand it, there is a way to tell the

Re: Stack file format change in 2.7 - BACK UP!

2006-04-20 Thread Chipp Walters
Hi Dave, I had contacted Mark a bit ago about the stackFileVersion property and he said it's ok to mention it, but it might be renamed or go away later, so it's not officially supported. If you click the 'update' button on the StackFormat plugin of mine, you'll download a new version which i

Re: Stack file format change in 2.7 - BACK UP!

2006-04-20 Thread David Burgun
Hi All, I really can't understand all the mystery surrounding this "fix" to allow backwards compatibility. As far as I understand it, there is a way to tell the engine to save in the old format or the new format, with version 2.7 defaulting to the newer format. That all sounds reasonable.

Re: Stack file format change in 2.7 - BACK UP!

2006-02-23 Thread Thomas McGrath III
Thanks J, This does clear things up for me. It is totally understandable now why they need to upgrade the version number and that it is normal too. Thanks Tom On Feb 23, 2006, at 6:53 PM, J. Landman Gay wrote: Rob Cozens wrote: Jacque, et al: It isn't any different than when HyperCard m

Re: Stack file format change in 2.7 - BACK UP!

2006-02-23 Thread J. Landman Gay
Rob Cozens wrote: Jacque, et al: It isn't any different than when HyperCard made the change Unless memory fails me, yes it is: that upgrade was free to owners of the previous version. I believe the 2.x update happened when HC was moved to Claris and we had to start buying our copies. At

Re: Stack file format change in 2.7 - BACK UP!

2006-02-23 Thread Rob Cozens
Jacque, et al: It isn't any different than when HyperCard made the change Unless memory fails me, yes it is: that upgrade was free to owners of the previous version. Do you intend to distribute all future stacks you release publicly in v.2.7+ and leave people who continue to work in v<2.7

Re: Stack file format change in 2.7 - BACK UP!

2006-02-23 Thread J. Landman Gay
Rob Cozens wrote: Jacque, et al: The stack file format in 2.7 has changed. Be aware that any stacks you save in 2.7 will not open again in earlier versions. Runtime Revolution, like HyperCard, now has different versions of software in use around the world producing incompatible output. Wha

Re: Stack file format change in 2.7 - BACK UP!

2006-02-23 Thread Eric Chatonet
Hi everyone, I second Rob with all my might. The result of this format change is pathetic. This means that Rev 2.6.1 *must* be used to build stacks able to be shared with the community (i.e. without the ability of using next Rev versions enhancements). And for those who will not have Rev pri

Re: Stack file format change in 2.7 - BACK UP!

2006-02-23 Thread Eric Chatonet
Hi everyone, I second Rob with all my might. The result of this format change is pathetic. This means that Rev 2.6.1 *must* be used to build stacks able to be shared with the community (i.e. without the ability of using next Rev versions enhancements). And for those who will not have Rev pri

Re: Stack file format change in 2.7 - BACK UP!

2006-02-23 Thread Rob Cozens
Jacque, et al: The stack file format in 2.7 has changed. Be aware that any stacks you save in 2.7 will not open again in earlier versions. Runtime Revolution, like HyperCard, now has different versions of software in use around the world producing incompatible output. What does this mean fo

RE: Stack file format change in 2.7 - BACK UP!

2006-02-13 Thread MisterX
t; Subject: Re: Stack file format change in 2.7 - BACK UP! > > I wrote: > > Just a word of warning. The stack file format in 2.7 has > changed. Be > > aware that any stacks you save in 2.7 will not open again > in earlier > > versions. Make backups if you

Re: Stack file format change in 2.7 - BACK UP!

2006-02-13 Thread J. Landman Gay
I wrote: Just a word of warning. The stack file format in 2.7 has changed. Be aware that any stacks you save in 2.7 will not open again in earlier versions. Make backups if you plan to work on stacks later with older engines. This behavior is marginally documented in the What's New file, but

Stack file format change in 2.7 - BACK UP!

2006-02-13 Thread J. Landman Gay
Just a word of warning. The stack file format in 2.7 has changed. Be aware that any stacks you save in 2.7 will not open again in earlier versions. Make backups if you plan to work on stacks later with older engines. This behavior is marginally documented in the What's New file, but doesn't s