On Mon, 14 Apr 2008 23:27:25 -0400, Gregory Lypny
<[EMAIL PROTECTED]> wrote:
Hello everyone,
I put the handler below into a field to experiment with mouseMove and
mouseLine. Unfortunately, the handler continues to operate even when
I select the Edit tool!
Gregory
In the discussion
Thanks Scott and Richard,
Crystal clear, and a useful insight into Rev's IDE and engine.
Gregory
Scott replied to me:
If you think abut it, this makes sense: Rev allows you to build your
own
authoring tools, which may need to utilize mouseMove messages in
pointer
tool mode, the sam
Gregory Lypny wrote:
...even when I select the Edit tool!
Scott touched on this, but it's worth at least a little more explanation.
What the Rev IDE may call the "edit tool", the engine knows as the
"pointer tool".
The engine provides a variety of tool modes to enable an astounding
variet
Recently, Gregory Lypny wrote:
> Never thought of that. But it's still a little disconcerting that the
> runtime environment is bleeding into the development environment.
> I've never encountered anything like that before.
If you think abut it, this makes sense: Rev allows you to build your own
essage: 22
Date: Mon, 14 Apr 2008 20:30:44 -0700
From: Scott Rossi <[EMAIL PROTECTED]>
Subject: Re: mouseMove Bug
To: Revolution Mail List
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="US-ASCII"
Recently, Gregory Lypny wrote:
I put the handler
Recently, Gregory Lypny wrote:
> I put the handler below into a field to experiment with mouseMove and
> mouseLine. Unfortunately, the handler continues to operate even when
> I select the Edit tool!
You could try adding the following:
> on mouseMove
if the tool <> "browse tool" then pass
Hello everyone,
I put the handler below into a field to experiment with mouseMove and
mouseLine. Unfortunately, the handler continues to operate even when
I select the Edit tool!
Gregory
on mouseMove
if the mouseChunk is not empty
then
put the value of the mouseLine
se
