Mark Schonewille wrote: > Op 10-aug-2007, om 16:14 heeft Mikey het volgende geschreven: > >> Is there some way to read-only a stack but not do it in such a way as >> to make fields and the like unusable? > > set the cantModify of stack "Stack Name" to true
The cantmodify will certainly prevent unwanted saves, but it may be worth noting that saving is always under the developer's control anyway.
This is in contrast to HyperCard and SuperCard, which automatically save and you have no control over it.
But with Rev, saving only occurs if you issue a save command a stack isn't saved when it's closed, so subsequent sessions will continue to show the stack in the same state as when you had last saved it, regardless of any changes made without a save command.
-- Richard Gaskin Managing Editor, revJournal _______________________________________________________ Rev tips, tutorials and more: http://www.revJournal.com _______________________________________________ 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
