cantSelect

[Richard Gaskin]

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 ordinary ones.
>
> 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 somewhere, and how to get to them?

It's trapped by the IDE whenever the pointer tool is active in order to 
prevent layout operations from triggering mouseUp handlers designed for 
browse tool use.

I submitted a request in 2006 to have this noted in the docs:

'Dictionary entries should note when message behavior is altered by the IDE'
<http://quality.runrev.com/qacenter/show_bug.cgi?id=2235>


If you can describe a bit more about what you're looking to do, Imay be 
able to help find a solution for your circumstance.  I've spent a lot of 
time working around this in both Rev and MC, and working around the 
workaround in a standalone where this isn't an issue (but other pointer 
tool things are).

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'
<http://quality.runrev.com/qacenter/show_bug.cgi?id=2606>


Many such circumstances could be avoided altogether if we had the 
ability to limit the scope of a tool mode to a group:

'tool property for groups/creating objects in groups interactively'
<http://quality.runrev.com/qacenter/show_bug.cgi?id=623>


--
  Richard Gaskin
  Fourth World
  Rev training and consulting: http://www.fourthworld.com
  Webzine for Rev developers: http://www.revjournal.com
  revJournal blog: http://revjournal.com/blog.irv