-
Notifications
You must be signed in to change notification settings - Fork 17
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
Interface layout Suggestion toward enhanced usability ... #67
Comments
Hi, |
Interesting idea ... Keyboard shortcuts. I'm kind of looking foreword to,trying that ... Do you need any beta testers ? Please forgive any spelling errors as this message was sent from a mobile.
|
I will try to work on this in a few days. If your OK, I will send you a proof of concept to get your feedback on the keyboard shortcuts feature. |
Released in RPB Chessboard version 4.4. |
I LOVE this plugin ... using it a LOT !!!
I do LOTS of Custom Setups ... (setting up for the black pieces are quick and easy, ...
but setting up for white takes much longer with a touch pad type mouse ... the piece-selection items for White pieces is currently at the top of the chessboard ... which typically opposite of the board where the pieces are most often placed ... this requires a lot of back-and-forth mouse travel - which is kind of painful for mousepad users, like myself.
Would it be better to have one row for the BLACK-piece selection items at the TOP (where it is now) ... and move the WHITE-piece sections row to the BOTTOM of the chess board, closer to where they are typically set up? ... This would shorten the back-and-forth mouse trips between different piece selection and make for quicker, easier setups. :-)
Not a big deal for regular mouse users, but a HUGE advantage for mousepad users!
(Of course enabling the "Flip Board" view setting would cause the piece-selection colors to flip as well ... )
Perhaps this is a lot of code ... but, it would certain enhance functionality ... pretty good GUI design already, but this would be a possible improvement.
(apologies, but I can not seem to figure out how to convert this post from an issue to a FEATURE REQUEST ).
The text was updated successfully, but these errors were encountered: