> > Like with fields, you can not store user information in a custom property > in an application (or standalone). >
This isn't quite right. On the mac, I can save data to a separate stack INSIDE of a standalone package with no problem. Not always the best place to put the data in some situations, but it works. Stephen Barncard ------------------------- San Francisco Stephen Barncard ------------------------- San Francisco 2009/2/16 Bob Sneidar <[email protected]> > Hi Mark. > > Thanks. I do understand that properties are persistent so long as a > standalone is running. I understand that Revolution standalones will not > save the state of properties when you quit them. I was saying that > Applescript standalones CAN and DO save the state of properties when they > quit, so that when you start up again they have the values you set them to > before you quit. The only time you lose them is when you recompile the > standalone (of course). > > I was just thinking in some future rendition of Revolution, maybe they > could pull that off, by saving the states of the properties internally to > the package itself. Barring that, maybe having a seperate "runtime engine" > similar to what Foxpro used to use, which did not allow development, but > only allowed execution of stacks would be possible. > > BTW I tested the theory that an app cannot be modified while running. This > is not true. I opened TextEdit and while it was running I opened the package > contents and edited a plist file using PlistEditPro. I changed one of the > values and saved the plist successfully. Wouldn't an internal property plist > file do nicely for just this sort of thing? > > Bob Sneidar > IT Manager > Logos Management > Calvary Chapel CM > > On Feb 14, 2009, at 1:48 PM, Mark Wieder wrote: > > Robert- >> >> Saturday, February 14, 2009, 1:27:33 PM, you wrote: >> >> I suppose where I was getting confused is that Applescript apps >>> properties are persistent. I just assumed rev apps pulled the same >>> kind of trick. >>> >> >> Methinks you're still a bit confused about this. >> Custom. Properties. Are. Persistent. >> >> The "problem" with standalone apps is that they can't be modified >> while they're running. So any changes you make in memory aren't (and >> can't) be saved to the running application. This is an operating >> system thing, not a rev thing. There are various ways to work around >> this: preferences files, splash screen apps, separate stack files, >> etc. >> >> -- >> -Mark Wieder >> [email protected] >> >> _______________________________________________ >> use-revolution mailing list >> [email protected] >> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >> http://lists.runrev.com/mailman/listinfo/use-revolution >> > > > _______________________________________________ > use-revolution mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
