Metacard is probably the only authoring system without an "author mode"
that really stops all handlers in the scripts of a stack.
I have seen the need for such a feature again twice during the last week
- students trying to look at some of the scripts in the demo stack
- a stack I was working on myself , where the opening black card blends
completely with the black backdrop and then leads to another card with a
visual effect triggered from the opencard handler of the first (black)
card. To access the first card (for changing the script) is only
possible through msg with "lock messages; go to cd 1".
This is not so simple as stated in the quoted message below, because you
have to know how to do this. Additionally there is no information
concerning the use of the msg in the helpfiles to use the semicolon when
you want to send more than 1 command.
>From the earlier discussion:
On May 3rd 2000 Scott wrote in response to Sivakatirswami:
> > Whats needed is a "global static" mode.
>
> The solution is much simpler: just lock messages before you go to the
> card. For example running "lock messages; go next" in the message box
> will do what you want. Tuv Snyder told me he even put a button in the
> Navigator palette that allows selecting this behavior, a modification
> I recommend if you do this kind of thing a lot.
> Regards,
> Scott
>
and Kevin on 04 May 2000 added responding to the same message:
> This will be supported from the first release of our development UI.,
>
presumably meaning to have such a "static mode" available in Revolution,
which up to date in not the case.-
I think we really could use an "author" or "static" mode as common in
other authoring tools.
Is not having an "author mode" in Metacard just a relic from earlier
stages of development that never has been amended or are there specific
advantages not to have such mode?
The "author mode" could easily be connected to the pointer tool.
Regards,
Wilhelm Sanke
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
