Ken Ray wrote:
>Well, we have the "newTool" message, which is sent when a tool is
chosen, so it could be used to detect when the browse tool is selected:
on newTool pTool
if pTool is "Browse" then
... (etc.)
end if
end newTool
However personally I'd like to see that message have an alternate
version called "toolChanged" to go along with "nodeChanged",
"selectionChanged", and "selectedObjectChanged".
And you could use the "startup" message to trap the starting up of your
standalone, since it is only sent to the first stack that is opened from
the engine (either the first RevIDE stack (if in the IDE), or the stack
opened first in your standalone).
Would these cover the bases of (1) for you?
------------------------------------------------------------
To a fair degree, I certainly think so Ken. However, the advantage of my
suggestion would be a greater unification between the "running" of the
project and the "running" of the standalone. At the moment, projects and
standalones (probably for historical reasons among others) seem to be 2
sorts of animals requiring perhaps different programming procedures.
This really does bother me. Of course, if "newTool" or "toolChanged"
could be executed at the beginning of the standalone, it would achieve
my objective.
Bob
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
