Separate scrolling from clicking#603
Conversation
It seems this edge case slipped through here. Currently, the selection starts from where the mouse is first moved, rather than where the button-down was initiated. Edit: In case it is of interest, I rebased my branch just to fix it locally, still seems sound to me. I still feel like it might be of some value in terms of reasoning, Cheers~ |
|
I don't doubt that your diff solves the issue but I'm trying to fit it into a long term solution where scrolling isn't the same as clicking in the first place. Dragging should also not be a boolean member like that, but rather the UI system should have distinct mouse-down/up events. Basically, I'm looking for a holistic solution rather than an immediate fix. |
|
I've filed #608 to track this. |
Without a node-path check, the order of UI element creation mattered. Since models are created after the text area this meant that the text area would steal all scroll input. This regressed in #603
Closes #410
Closes #588