-
Notifications
You must be signed in to change notification settings - Fork 30
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
Move tool sometimes doesn't send ChangeBoundsAction #22
Comments
Btw, this seems to cause the intermittent resets of positions after moving and receiving an update model that is also reported in eclipsesource/graphical-lsp#342. |
planger
added a commit
that referenced
this issue
Dec 23, 2019
martin-fleck-at
pushed a commit
that referenced
this issue
Jan 8, 2020
martin-fleck-at
pushed a commit
that referenced
this issue
Jan 8, 2020
holkerveen
pushed a commit
to holkerveen/glsp-client
that referenced
this issue
Dec 21, 2024
…glsp#22) (eclipse-glsp#23) With this change, we don't rely on the positionDelta for sending out mouse ChangeBoundsActions but only check whether we started dragging via lastDragPosition. Resolves eclipse-glsp#22 and also fixes eclipse-glsp#21 while we're at it.
holkerveen
pushed a commit
to holkerveen/glsp-client
that referenced
this issue
Dec 21, 2024
…glsp#22) (eclipse-glsp#23) With this change, we don't rely on the positionDelta for sending out mouse ChangeBoundsActions but only check whether we started dragging via lastDragPosition. Resolves eclipse-glsp#22 and also fixes eclipse-glsp#21 while we're at it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you drag an element for a bit back and forth the move tool doesn't send out a
ChangeBoundsAction
eventually. This seems to be fixed, when just checking whether alastDragPosition
exists and not if there actually is apositionDelta
.The text was updated successfully, but these errors were encountered: