Mark Wieder wrote:
Björnke-
Tuesday, June 8, 2010, 1:02:27 AM, you wrote:
I can't speak for Mark, but in the mentioned case it's sufficient
to "go" to your stack, and depending on your needs, you can do it
invisible:
go invisible stack "valid/path/test.rev"
...you can go ahead and speak
Björnke-
Tuesday, June 8, 2010, 1:02:27 AM, you wrote:
> I can't speak for Mark, but in the mentioned case it's sufficient
> to "go" to your stack, and depending on your needs, you can do it
> invisible:
> go invisible stack "valid/path/test.rev"
...you can go ahead and speak for me...
That'
On 8 Jun 2010, at 02:41, Bob Sneidar wrote:
> Hi Mark.
>
> By Loading Into Memory, do you mean the "Start Using" command?
>
> Bob
I can't speak for Mark, but in the mentioned case it's sufficient to "go" to
your stack, and depending on your needs, you can do it invisible:
go invisible stack
On Tue, Jun 8, 2010 at 5:12 AM, Peter Haworth wrote:
>
> When my application starts up, I'll retrieve all these property values and
> set them into the objects that own them. I'll have to find a mechanism to
> prevent the setProp handler from updating them again during that process but
> some sor
Hi Mark.
By Loading Into Memory, do you mean the "Start Using" command?
Bob
On Jun 6, 2010, at 8:41 PM, Mark Wieder wrote:
> You *can* tell the standalone builder to make the substacks separate
> files in the build phase. This will get around the problem sometimes.
> You do have to remember t
any input on this idea..
Pete Haworth
On Jun 7, 2010, at 10:00 AM, use-revolution-requ...@lists.runrev.com
wrote:
Message: 8
Date: Mon, 7 Jun 2010 18:06:27 +0200
From: Mark Schonewille
Subject: Re: Saving Data in Standalones
To: How to use Revolution
Message-ID: <4d63dbd4-4428-40e3-9953
Pete,
Probably, you log in on your Mac with admin privileges. That gives you
write access to the applications folder. The guest account (Mac OS X
10.5 and later) and limited accounts don't have write access for the
applications folder and several other folders. That's why you should
avoid
Thanks for all the suggestions folks.
I've already set up a preferences file and rewritten the code that
opens my db to get it's path from there and store the path there if a
different db is opened and all works well. Thanks to Sarah Reicheldt
for the function that returns the user's Prefe
On Mon, Jun 7, 2010 at 5:53 AM, Peter Haworth wrote:
>
> I'm not concerned about saving my applications data across runs because I'm
> using an sqlite database for that. The stuff I need to preserve is more in
> the way of internal settings. I'd prefer to leave them in custom properties
> if I c
Pete-
Sunday, June 6, 2010, 2:53:37 PM, you wrote:
> Help!
You covered a lot of issues there. I see Mark S. has addressed one of
them already. Here's some more.
One of these is easy: if you want to prevent a rev script from being
loaded, poked into, and modified then set a password on the stack
Peter,
Just make sure that you write to a directory for which you have
permissions. Not the system directory or the application directory,
but preferably the documents directory or the preferences directory.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineer
Not again, I can hear some people saying!
I've just run into this long standing issue in the context of needing
to save the filepath to my database across runs of Revolution and also
various other settings I need to save which are currently in custom
properties.
I'm not concerned about sa
12 matches
Mail list logo
