If the run tool is for running a stack and the edit tool is for editing
it, why do scripts even run in edit mode? mouseEnter, mouseLeave,
openCard, closeCard, etc. all are executed even when the edit tool is the
one selected. But mouseDown and mouseUp aren't.
Does anyone else find this odd?
This feature makes it quite simple to create a simple drawing program.
And if you set up a stack as a palette (for example; actually
anything but a topLevel), it will behave as if in browse mode (the run
tool) regardless of which tool is selected. So you can have a
document window for the
Marty Billingsley wrote:
If the run tool is for running a stack and the edit tool is for editing
it, why do scripts even run in edit mode? mouseEnter, mouseLeave,
openCard, closeCard, etc. all are executed even when the edit tool is the
one selected. But mouseDown and mouseUp aren't.
The problem
At 12:51 PM -0500 10/23/2004, Marty Billingsley wrote:
If the run tool is for running a stack and the edit tool is for editing
it, why do scripts even run in edit mode? mouseEnter, mouseLeave,
openCard, closeCard, etc. all are executed even when the edit tool is the
one selected. But mouseDown