-
Notifications
You must be signed in to change notification settings - Fork 108
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
Deleting/cutting causes position of floated pixels to jump on first mouse motion #78
Comments
Yeah this isn't ideal. You can also nudge the selection with the I think the ideal UX for me would be:
|
This is odd though, you mean the cursor isn't centered in the selection when you move it? |
I can see the rationale, but I prefer to use For me, the ideal UX would simply be "the anchor point for the selection will be wherever the mouse was when
My mistake. I was tired and distracted and didn't notice that, when it was jumping the image out of alignment on pieces of little 8x8 sprites, it wasn't jumping it all the way. |
With rx 0.4.0, when I...
v
d
to cut the selection...as soon as I move my cursor, the selected block of pixels will jump so that the top-left pixel is under the cursor. This is a big inconvenience when I just want to move a block of pixels up/down/left/right a pixel or two relative to their original position because my habit of selecting from top-left to bottom-right invariably puts the cursor over the bottom-right pixel of the selection.
d
should either grab the floated selection based on where the cursor was at the timed
was pressed, relative to the selection or warp the pointer to the top-left corner of the floated selection.The text was updated successfully, but these errors were encountered: