stephen barncard wrote:
Remember a stack can both be a visible window with objects and
a holder for scripts, it can also be a very efficient and
addressable data container.
The stack one compiles as an app can call other stacks that are not
compiled. The best of both worlds.
Stack files
Hi everyone,
Thanks for all of your replies. Crystal clear. It has been a long time since
I've built a standalone since a lot of the stacks that I use for research are
used by me alone. I made the mistake of using substacks rather stack files and
a splash screen disguised as the main app as
Nope. Nothing can modify a compiled app, and you main app becomes part of the
application. Nothing gets saved.
There are a couple approaches to this:
1. Have you main stack be an application loading splash stack of some kind,
then hide it and load an included stack that is your REAL
You're not doing anything wrong - Revolution does not allow data,
custom props, etc to be saved in a standalone application. I was just
bitten by this a couple of weeks ago. I'm using a database to store
all my data so that wasn't an issue, but I also use custom props whose
settings have
Just to confirm, nothing does. It's not a Revolution issue, it's an executable
issue.
Bob
On Jul 1, 2010, at 2:59 PM, Peter Haworth wrote:
You're not doing anything wrong - Revolution does not allow data, custom
props, etc to be saved in a standalone application.
Remember a stack can both be a visible window with objects and a holder for
scripts, it can also be a very efficient and addressable data container.
The stack one compiles as an app can call other stacks that are not
compiled. The best of both worlds.
On 1 July 2010 15:01, Bob Sneidar
Gregory Lypny wrote:
I suspect this has come up before. I just built a standalone
version of a stack that allows users to import data into fields.
Custom props are set during a user's session and various other
changes occur. I have the following save handler in the stack
script, but when
The following from a S-Card user re changes in a distributed stack. Is
it really a laborious task to have cards save the data entered on
them in a distributed stack or is there some nice checkbox to click
somewhere?
If I create a Rev stack and make a standalone of it, put it on
Because Mac OS (v 7 - 9) is not OS X !!!
Funny, I don't remember asking about OS 7-9
And so called Classic apps actually in the old Mac OS which runs as
an emulator of sorts within OS X. As far as the apps are concerned,
it's still Mac OS 9.
I bet Carbon apps can't modify
Because Mac OS (v 7 - 9) is not OS X !!!
It's worth noting that even though Mac OS allows an app to write
for itself,
Apple recommends storing user data outside of the app in a user folder, so
the following discussion would also benefit SC users looking to modernize
their apps:
If OS X is
On Tuesday, August 5, 2003, at 10:50 PM, Stephen Quinn Barncard wrote:
Because Mac OS (v 7 - 9) is not OS X !!!
And so called Classic apps actually in the old Mac OS which runs as
an emulator of sorts within OS X. As far as the apps are concerned,
it's still Mac OS 9.
I bet Carbon apps can't
John Tenny wrote:
The following from a S-Card user re changes in a distributed stack. Is
it really a laborious task to have cards save the data entered on
them in a distributed stack or is there some nice checkbox to click
somewhere?
If I create a Rev stack and make a standalone of
It's worth noting that even though Mac OS allows an app to write
for itself,
Apple recommends storing user data outside of the app in a user folder, so
the following discussion would also benefit SC users looking to modernize
their apps:
If OS X is based on UNIX and UNIX can't save to a
13 matches
Mail list logo
