Use precise coordinates in org.eclipse.gmf.runtime.diagram.ui.tools.DragEditPartsTrackerEx.snapPoint(ChangeBoundsRequest) #63
Milestone
Comments
lredor
added a commit
to lredor/gmf-runtime
that referenced
this issue
Apr 25, 2024
This was referenced Apr 25, 2024
lredor
added a commit
to eclipse-sirius/sirius-desktop
that referenced
this issue
Apr 25, 2024
This commit removes the code duplicated from GMF as the bug is now directly fixed in GMF (through issue eclipse-gmf-runtime/gmf-runtime#63). Bug: #378
pcdavid
pushed a commit
that referenced
this issue
Apr 30, 2024
lredor
added a commit
to eclipse-sirius/sirius-desktop
that referenced
this issue
Jun 27, 2024
This commit removes the code duplicated from GMF as the bug is now directly fixed in GMF (through issue eclipse-gmf-runtime/gmf-runtime#63). Bug: #378
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Sirius #359, a bug has been discovered in GMF. In the method org.eclipse.gmf.runtime.diagram.ui.tools.DragEditPartsTrackerEx.snapPoint(ChangeBoundsRequest) the x and y coordinates are used. But if the moveDelta is a
PrecisionPoint,preciseX()andpreciseY()should be used instead. Indeed, according to the zoom level, preciseX or preciseY can be something like 0.5 and must no be considered as 0.The text was updated successfully, but these errors were encountered: