Richard.
Thanks for the info. I worked around it.
The dictionary entry for cantSelect says: When the user clicks the
control with the Pointer tool, Revolution acts as though it has been clicked
with
the Browse tool.
This is what started me on this. No biggie. But I do agree that the SC
Richard-
Thursday, March 11, 2010, 10:21:59 PM, you wrote:
I much prefer the way SC handles the pointer tool, splitting messages so
there's a separate suite for when the pointer tool is active:
'Add pointerDown, pointerUp, pointerDoubleUp, etc. for when pointer tool
is active'
will be selected instead.
If you turn on that object's cantSelect property, you won't get the
marquee selection.
Same with responding to drops in your drawing region, and other mouse
actions in groups.
If you have time on your hands you can write several hundred lines of
code to emulate the pointer tool
I agree with Richard in spirit. But my pet peeve is the lack of mouse messages
and properties that are sent or set when the mouse is down (like for example
mouseLoc). especially for games, educational apps and graphing, this would be
similarly important.
On 12 Mar 2010, at 17:35, Richard
Back with this.
I am irked by the fact that when an object's cantSelect property is
true, messages like mouseUp are not sent when clicking with the pointer
tool.
I know I expect a lot in editing mode already, but the docs say it should
be so.
mouseEnter and mouseLeave are sent, but no other
Craig-
Thursday, March 11, 2010, 2:28:25 PM, you wrote:
The message watcher shows certain ubiquitous messages being sent in this
condition, like cRevGetsUpdate, but I cannot trap it (though I suspect I
will be told not to play with fire). Isn't there a list of these top secret
messages
Mark.
If I suppress setProps in the message watcher it still comes up. It has to
be a system message.
Craig
In a message dated 3/11/10 5:58:27 PM, mwie...@ahsoftware.net writes:
That sounds more like a setprop handler firing. Are you sure that was
a message? If it turns out to be a
Craig-
Thursday, March 11, 2010, 3:18:51 PM, you wrote:
If I suppress setProps in the message watcher it still comes up. It has to
be a system message.
From the messagebox type
revVerboseDebug true
then run your test and set it back to false. Look for a file called
verboseLog.txt (should be
DunbarX wrote:
I am irked by the fact that when an object's cantSelect property is
true, messages like mouseUp are not sent when clicking with the pointer
tool.
I know I expect a lot in editing mode already, but the docs say it should
be so.
mouseEnter and mouseLeave are sent, but no other
