Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The selected object should take priority for drag operations #33

Closed
qwertie opened this issue Nov 5, 2016 · 2 comments
Closed

The selected object should take priority for drag operations #33

qwertie opened this issue Nov 5, 2016 · 2 comments

Comments

@qwertie
Copy link

qwertie commented Nov 5, 2016

I'm drawing a diagram with boxes nested inside other boxes. While trying to resize the outer box, if an inner box is nearby then FlowSharp tends to prefer to drag that object instead, even if the resize handles of the selected box are closer to the mouse!

@cliftonm
Copy link
Owner

cliftonm commented Nov 6, 2016

I believe this issue has been corrected by a bug fix in the mouse controller. Actually what I consider to be a bug in .NET's mouse event, in that a mouse click also produced a mouse-move event. Because the mouse move event was initiating dragging the shape, rather than the anchor, I think this was the issue. The mouse controller now ignores mouse move events when the mouse hasn't actually moved. I recreated a test scenario with multiple nested boxes and everything worked correctly.

@cliftonm cliftonm closed this as completed Nov 6, 2016
@qwertie
Copy link
Author

qwertie commented Nov 6, 2016

What I'm talking about happens even before you click the mouse - the app shows before you click which object will be resized when you click and drag, and sometimes it's not the selected object that the mouse cursor is actually on, in case there's a nearby, nested shape.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants