Difference between revisions of "Cocoa Internals/Input"
(initial mouse event handling description) |
m |
||
| Line 7: | Line 7: | ||
However, such MouseMove events would be reported to the '''focused''' controls (aka FirstResponder), rather than the control immediately under the cursor. | However, such MouseMove events would be reported to the '''focused''' controls (aka FirstResponder), rather than the control immediately under the cursor. | ||
| − | + | (MouseDown, MouseUp events are reported directly to the control under the cursor, similar to LCL). | |
Because of that, Widgetset mouse event processing routine first checks, if cursor is actually above the focused control, and if it's not, it would let Cocoa propagate the mouse event, down (from child to parent) the controls hierarchy. | Because of that, Widgetset mouse event processing routine first checks, if cursor is actually above the focused control, and if it's not, it would let Cocoa propagate the mouse event, down (from child to parent) the controls hierarchy. | ||
| Line 14: | Line 14: | ||
If the actual control is found, the propagation of the event is stopped. | If the actual control is found, the propagation of the event is stopped. | ||
| + | ==See Also== | ||
| + | * [[Cocoa Internals]] | ||
[[Category:Cocoa]] | [[Category:Cocoa]] | ||
Revision as of 05:33, 18 July 2018
Mouse
The biggest difference between Apple and LCL ideology is the way of handling MouseMove events.
According to Apple - mouse events are easily to flood the event queue and thus are disabled by default, unless a use presses and hold the button.
Apple provides a special NSWindow mode to allow MouseMove events to come through even with buttons unreleased. However, such MouseMove events would be reported to the focused controls (aka FirstResponder), rather than the control immediately under the cursor.
(MouseDown, MouseUp events are reported directly to the control under the cursor, similar to LCL).
Because of that, Widgetset mouse event processing routine first checks, if cursor is actually above the focused control, and if it's not, it would let Cocoa propagate the mouse event, down (from child to parent) the controls hierarchy.
Such propagation happens, when NSView inherited mouseMove event is called.
If the actual control is found, the propagation of the event is stopped.
