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
Modify Table list selection can be 'fooled' by dragging #261
Labels
bug
Confirmed bugs or reports that are very likely to be bugs.
Milestone
Comments
justinclift
added
the
bug
Confirmed bugs or reports that are very likely to be bugs.
label
Apr 15, 2015
Thanks, that definitely sounds like a bug. 😉 |
MKleusberg
added a commit
that referenced
this issue
Apr 17, 2015
MKleusberg
added a commit
that referenced
this issue
Apr 17, 2015
Haha nice find 👍 Thanks for reporting! |
@EArmour Would you be ok to try out the next nightly build (tomorrow), and let us know if it's working like it should now? 😄 |
Alright, looks good now! Thanks for the quick response 👍 |
Awesome! Thanks for letting us know @EArmour. 😁 |
MKleusberg
added a commit
that referenced
this issue
Apr 23, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is occurring in the latest nightly Windows build.
When modifying the order of fields, the 'move up/down' buttons are disabled when at the top/bottom of the list. But if you click on another row, then hold down the mouse button and drag to one of the end rows, the movement buttons are not properly disabled. So you can click to move the top row up and the bottom row down, both of which crash the application.
The inverse also works, so if you click the bottom row, then drag up one row, the "move down" button will be disabled even though you should be able to move the field. So basically it seems like the listener for disabling those buttons triggers on the mouse click, not the actual final selection after dragging around.
The text was updated successfully, but these errors were encountered: