HyperCard Headstart, Part Threeby J.R. Mooneyham
ORIGINAL PUBLICATION DATE: FALL 1994(?)
(Translate this site)
| Search this site | Site map | Site author | Site store |
>>> | Latest site updates | <<<
Alternative (mirror site) links
| Translate this site |
| Site search | Site map | Site author |
| Access Google's cache of this site |
markedproperty in its Info dialog, and add the word
markedto scripts containing
gocommands, like so:
go to next marked cd.)
markedproperty helps you not only to discriminate about which cards a user sees, but about which ones they may print as well.
desperadohandler, put the
desperadohandler in the background script and all will have access to it. If you have other cards requiring this handler, but they possess a different background, you can locate
desperadoin the stack script instead of a background script, in order to make it available to all.
lock screencommand described previously can help significantly in speeding up script execution, if one aspect of the script involves a lot of visually perceptible actions.
lock screenessentially turns off all graphic output, and so removes that processing load from the total burden of the HyperCard engine carrying out your script instructions.
sendcommand is one of the more powerful HyperCard elements, using it can also slow script execution. So avoiding it speeds things up a bit.