-
Notifications
You must be signed in to change notification settings - Fork 423
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
[BUG] DrawingView drawing continues even after mouse release #1671
Comments
I am not sure we can control if the user released the button outside the control. probably the event won't be triggered. |
I think that is a decent solution for this problem. |
I found a solution for anyone interested:
This mostly replicates the behavior from other platforms, except that the drawing is restarted when the pointer enters the DrawingView, even if the mouse button was released and pressed again outside the bounds of the DrawingView. |
I had the same issue that drawing lines continued out of bounds. But....when using DrawingView.GetImageStream() the lines out of bound suddenly appeared in the saved/captured image. For this I made a workaround using CaptureAsync().....for anyone interested
This crops the image to the only visible part. |
Is there an existing issue for this?
Did you read the "Reporting a bug" section on Contributing file?
Current Behavior
When user clicks inside the DrawingView control and starts drawing, later user releases the mous outside the DrawingView control. Afterwards user comes back the DrawingView control without pressing the mouse left button, the drawing will continue.
Expected Behavior
When user releases mouse outside the DrawingView should be considered as end of drawing. Thereafter, when user comes inside the control should not continue the drawing.
Steps To Reproduce
Link to public reproduction project repository
Not yet
Environment
Anything else?
Mouse should be captured during the start of drawing, later MouseCapture release event should be listened and stop the drawing.
The text was updated successfully, but these errors were encountered: