How do I stop app's files from being opened by Rev?
Barry Levine
themacguy at macosx.com
Thu Aug 7 10:18:02 EDT 2003
Jacqueline,
I'm familiar enough with the Mac to know how to use ResEdit to change
type/creator codes so the problem is really on the Windows side of
things. The extension change seems to be the best answer (it does work)
as long as I call the stack in my code (go stack "myStack") instead of
the file containing it (go stack "myStack.rev") or change the extension
in my code (go stack "myStack.xxx").
It's funny how Rev permits you to refer to the file as the stack.
That's not a complaint. What I love about Rev (and it's what I loved
about HyperCard) is its ability to deal with synonyms in its code. It's
the closest thing to the "do what I mean" button.
Of course, this ability to use sloppy code can (and does) create issues.
Regards,
Barry
On Wednesday, Aug 6, 2003, at 23:46 America/Denver, Jacqueline wrote:
> From: "J. Landman Gay" <jacque at hyperactivesw.com>
> Organization: HyperActive Software
> To: use-revolution at lists.runrev.com
> Subject: Re: How do I stop app's files from being opened by Rev?
> Reply-To: use-revolution at lists.runrev.com
>
> On 8/6/03 5:08 PM, Barry Levine wrote:
>
>> I'm guessing that, on the Mac, I'd drop the two apps inside the
>> "package" of the app. I remember seeing a reference how to do this in
>> the list and I'll search for it.
>
> That's probably a good way to do it. If you are distributing for OS 9
> though, there is no package. One way to handle it is to assign a
> different file type code to the stacks. That way Rev won't allow the
> user to select them in a standard file dialog, but it can still open
> them from a script.
>
>> On Windows, I haven't a clue.
>
> I don't know if this is kosher or not, but I usually just assign a
> ".dat" extension. Windows thinks the stack is a data file, it gets a
> generic icon, and it doesn't seem to get in the way of anything. If you
> want to be really sneaky, password-protect the stacks. Then if someone
> opens them in a text editor, they look like binary files and no text is
> visible.
>
More information about the use-livecode
mailing list