And in order to keep the distributable 'stack' within you app theme:
You could append a different extension, for example 'ebook2.ebk'
instead of 'ebook2.rev' and rename it internally.
Cheers,
Luis.
On 8 Nov 2007, at 13:50, Björnke von Gierke wrote:
On 08 Nov 2007, at 14:12, Paul Robinson wrote:
If there is a sample stack or some script anyone has could you
help please?
If you have a stack to save, try something like this in a button:
on mouseUp
answer file "where to save the stack?"
if it <> "" and the result = "" then
put it & ".rev" into thePath
end if
save stack "name of your stack goes here" as thePath
end mouseUp
Note that you cannot edit an executable, so you can't save the
substack into the executable itself. On Mac OS X, executables are
contained within a bundle folder, which you can theoretically put
stuff into, but Apple is not fond of that, and the newest OS
(leopard) will put up a dialog if you try to reopen an application
edited in this way.
Because of this, you're best served by creating a document
paradigm, letting users send individual stack files around, and
open them with your application.
Bjoernke
--
official ChatRev page:
http://chatrev.bjoernke.com
Chat with other RunRev developers:
go stack URL "http://homepage.mac.com/bvg/chatrev1.3.rev";
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
