Hi, Hannes.

The generic event handler, which can be configured via #on:send:to:, kicks
in at the level of Morph >> #mouseDown: here. For historic reasons, the halo
invocation kicks in earlier at the level of Morph >> #handleMouseDown:.
Well, since #handleMouseDown: is considerend framework code and #mouseDown:
application code, this is a good thing because applications cannot easily
overwrite the halo functionality. However, we should, for the future, make
the means of interaction for halo invocation configurable so that there is a
chance for applications to make use of the blue button at all. For example,
if you do not need [CMD]+[SHIFT]+[B] in your application, you may want to
re-map halo invocation to that. :-) An event filter could be used to achieve
this.

Best,
Marcel



--
View this message in context: http://forum.world.st/Mouse-button-tester-question-tp4941095p4952911.html
Sent from the Squeak - Dev mailing list archive at Nabble.com.