>From: Dave Cragg <[EMAIL PROTECTED]>
>If you don't want to mess around with the development environment,
>another approach is to make a "utility stack" for each project you
>are working on. You can add buttons to these stacks that perform
>frequently used operations. (Anything you find yourself typing in the
>message box repeatedly).
>
>For navigating through cards while suppressing messages:
>
>lock messages
>go next card of stack myStack
>
>Other functions I commonly add to such stacks:
>
>deleting a stack from memory after it has been closed
>deleting globals that are created by the stack being developed
>(Both of these are useful for creating a clean environment when
>testing initialization routines. They can save you having to restart
>Metacard.)
>
>opening scripts for editing of stacks that are currently closed
>(modal dialogs, for example)
>
>and so on :)
>
>The ease of being able to make such stacks in Metacard can be a real
>productivity boost.
>
>Cheers
>Dave Cragg
I created a similar stack for my most recent project, but didn't
think to include some of the features suggested here. Based on your
message, Dave, I now suspect that creating stacks of this type is a
common practice. I propose we begin sharing more of these home-grown
development utilities, creating a library of solutions to common
problems and a treasure-trove of scripting tricks. I think many of
us would benefit from this, but especially the newcomers to MetaCard.
I will have several such stacks to share in the next few weeks. Is
there a common place where we can post them, along with a sentence or
two of description?
Craig
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
Craig Spooner
Office of Instructional Services
Colorado State University
970-491-2516
[EMAIL PROTECTED]
Archives: http://www.mail-archive.com/metacard%40lists.best.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
