2fast-team
[Feature] Improve key value selection
Describe the problem this feature would solve
As a programmer, I'm rather focussed to handle apps using the keyboard than using the mouse or other gesture device. That's why I'd like to suggest to improve accessibility of the 2fast app by adding more keyboard shortcuts. This would ease handling a lot.
Describe the solution
-
When the app opens, the list of registered clients should receive focus from the beginning.
-
The list of registered clients should be scrollable using cursor keys, like UP ARROW / DOWN ARROW / HOME / END / PAGE UP / PAGE DOWN.
-
Hitting ENTER (or RETURN, resp.) should copy the corresponding list item's current value to the clipboard:
-
Moreover, hitting any of the number keys (1 to 0) should copy the corresponding list item's current value to the clipboard:
This way, the first 10 list items' values can easily and quickly be copied. -
Finally, I suggest the clickable area for copying a list item's value to be extended to encompass all three StackPanel items:
- The current value
- The copy icon
- The countdown icon
This will make it easier to copy the current item's value using the mouse or similar gesture device without giving it too much thought.
Thank you for the corresponding suggestion :)
The implementation would be done in several steps, as the implementation of copying the code with tab and enter was easy to implement at first.
The start and order of tab navigation is something i need to look at, this will probably require an option in the settings to not change the operation by default for ease of use or for the controller.
Today I updated to the latest version. I looks like none of the changes you described is available in the production version yet?
The change was implemented after the release of current version 1.2.6, this will definitely be included in the next maintenance update 1.2.7.
This turns out to be more difficult than expected with the tab input. The initial main shell brings the focus to the hamburger button every time, but I don't want to overwrite the design instead only set the focus in the code behind. Even a focus on the listview of the accounts only works correctly once a navigation has been executed again.
The extended input with numbers should work if a control command is included (CTRL or something else).
Thank you for your kind reply!
Hmm, this is an UWP app, isn't it? Would the following suggestion help?
https://learn.microsoft.com/en-us/answers/questions/566115/how-to-set-focus-on-a-primary-button-in-an-input-d#answers
(It's making use of the form's GotFocus event.)
Yes, it is exactly this function, but it does not work immediately after logging in, it only works after a navigation, e.g. to the settings. This is still a puzzle that needs to be solved.
But I have implemented point four from your suggestion in version 1.3.1, see the RC release https://github.com/2fast-team/2fast/releases/tag/v1.3.1-rc1.
If the list of accounts has the focus, you can navigate to the account by holding down the menu button (ALT) and entering the corresponding number (even with more than 9 accounts) and releasing the menu button.
Today, I downloaded the latest 2Fast version.
Yet, I couldn't see suggestion 4 working. When I hit ALT+1 or ALT+2, nothing happens.
Did you have a chance of implementing suggestion 5 yet?
Currently, I am learning MAUI. Perhaps I will find a solution to suggestion 1.
Yet, I couldn't see suggestion 4 working. When I hit ALT+1 or ALT+2, nothing happens.
The problem is here the auto focus on the hamburger button (main shell). If the list view of the accounts is selected, holding ALT, enter the number and release ALT will work.
Did you have a chance of implementing suggestion 5 yet?
Currently, there are a option implemented to right-click anywhere on an account item to trigger the copy to clipboard. Therefore, I am uncertain whether additional copying mechanisms are necessary.
Currently, I am learning MAUI. Perhaps I will find a solution to suggestion 1.
At MAUI, with the target of WinAppSDK/WinUI3, the problem should be reproducible if you use a main shell.
I am currently working on making the application fully compatible with AOT compilation on .NET 10, which will also benefit the iOS and Android applications that have not yet been released and enable them to be published.