Disabled files in 2.7 - Followup
simplsol at aol.com
simplsol at aol.com
Sat Feb 18 12:05:23 EST 2006
Mark,
What if the developer wants to use his own Creator code, so that stacks
open with a standalone. It appears that this code is being overwritten
when that stack is edited in Rev.?
Paul Looney
PS Thank you for responding so promptly.
-----Original Message-----
From: Mark Waddingham <36degrees at runrev.com>
To: How to use Revolution <use-revolution at lists.runrev.com>
Sent: Sat, 18 Feb 2006 11:26:33 +0000
Subject: Re: Disabled files in 2.7 - Followup
Hi Paul,
Thank you for bringing this to our attention.
I've just looked at this and it would seem that the cause is that the
'stackFileType' global property is being inadvertently set to 'MacOS' -
rather than 'RevoRSTK' or 'MCRDMSTK'. The 'stackFileType' global
property (which is readable and writeable) determines the creator and
file type codes that stacks are saved with.
(The reason for existence of this property is so that developers
producing systems in Revolution that base their file-format on
Revolution stacks can tie their files to their environment, rather than
the Revolution or MetaCard IDE)
If you do:
set the stackFileType to "RevoRSTK"
in the message box on startup all stacks saved in that session should
then have the appropriate file type and creator code set. (Of course,
we will fix this underlying default issue - this is just to help make
life easier for you in the mean-time).
In terms of opening stacks, then do remember you can choose to display
'All Files', instead of just those identified by either a '.rev'
extension, a '.mc' extension or a 'RevoRSTK', or 'MCRDMSTK'
file/creator type.
Also, Revolution itself does not use either the extension nor the
creator or file-type to determine whether a file is a Revolution stack
or not. Instead, it checks the header to see if it conforms to the
file-format. This means that the engine will attempt to load any file
you give it as a stack file - and it will return an appropriate error
message if it finds that it is not.
Warmest Regards,
Mark.
On 18 Feb 2006, at 02:41, simplsol at aol.com wrote:
> Jacque,
> My pleasure:
> It is now bug 3336
> Paul Looney
>
> -----Original Message-----
> From: J. Landman Gay <jacque at hyperactivesw.com>
> To: How to use Revolution <use-revolution at lists.runrev.com>
> Sent: Fri, 17 Feb 2006 15:56:42 -0600
> Subject: Re: Disabled files in 2.7 - Followup
>
> simplsol at aol.com wrote:
>
> > The original 2.6.1 Type and Creator are
> > RSTK and Revo
> > After opening a stack in 2.7 the Type and Creator are converted to
> > STK and MacO
>
> This has got to be a bug. The plist for Rev 2.7 still lists "RSTK" >
as the proper file type, and the creator code is still "Revo".
>
> I looked at a newly saved stack and saw that the creator was >
"MacO" and the file type was "ST<littlebox>K". It is the incorrect >
file type that will prevent stacks from opening, but the creator > code
needs to be fixed as well.
>
> Can you bugzilla this for us?
> -- Jacqueline Landman Gay | jacque at hyperactivesw.com> HyperActive
Software | http://www.hyperactivesw.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
>
> _______________________________________________
> 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
>
------------------------------------------------------------------
Mark Waddingham ~ 36degrees at runrev.com ~ http://www.runrev.com
Runtime Revolution ~ User-Centric Development Tools
_______________________________________________
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