Skip to content
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

Preferences window does not support keyboard navigation #10005

Open
2 tasks
bershanskiy opened this issue Jun 19, 2021 · 6 comments
Open
2 tasks

Preferences window does not support keyboard navigation #10005

bershanskiy opened this issue Jun 19, 2021 · 6 comments
Labels
Status: Needs Info Needs more information before action can be taken. Status: Stale ⌛ This issue is over a year old. It might be obsolete or just needs a fresh set of eyes Type: Bug The code does not produce the intended behavior.

Comments

@bershanskiy
Copy link

Application Version

4.9.1

Platform

Windows 10

Printer

N/A

Reproduction steps

  1. Open Cura
  2. Via the program menu open "Preferences" window (click "Preferences" > "Configure cura..."
  3. Click on "General" to highlight it
  4. Press down key and up key to select amy other section of the menu

Actual results

Nothing happens besides highlight moving from one preference section title to another.

Expected results

When highlight moves from one preference section title to another, that section is opened. This would be consistent with other programs.

Checklist of files to include

  • Log file
  • Project file

Additional information & file uploads

Apparently, there is no way to switch to another section without using a mouse.

@bershanskiy bershanskiy added the Type: Bug The code does not produce the intended behavior. label Jun 19, 2021
@fvrmr
Copy link
Contributor

fvrmr commented Jun 21, 2021

Hi @bershanskiy thank you for your report.
I checked versions 4.7 to 4.10 and your expected result doesn't happen in the other versions. So your report is more a feature request instead of a bug.
I will bring this up with the team. Keep you posted.

@Ghostkeeper
Copy link
Collaborator

I'm unable to reproduce this issue on Ubuntu. Keyboard navigation seems to work fine.
Demonstration: http://dulek.net/work/preferences_keyboard_navigation.webm

By clicking on an element it's clear to see where it's started. If you don't click anything first, pressing tab will first select the header which is not visible. But it'll continue with the real options after pressing tab a few times.

@rburema said he'd take a look on Windows to see if he can solve it, according to our meeting notes.

@rburema
Copy link
Member

rburema commented Jun 29, 2021

@Ghostkeeper That's not what they mean, I think. Go to 'general', then press 'down'; you don't go to the 'settings', or 'printers', or 'materials' menu's. So it's not about the menu's themselves.

I have a partial fix for this, but was stuck on the materials menu, which eats the focus (and the way it's set up, it needs it). So you can go down (or up) to the materials menu with the keyboard, and then it stays on there.

@rburema
Copy link
Member

rburema commented Jul 6, 2021

I made a ticket on our board to review the partial fix. (The partial fix itself can be seen here Ultimaker/Uranium@caf8a3c )

Fixing this completely would probably mean untangling the materials menu though, which is unlikely to happen soon.

@rburema
Copy link
Member

rburema commented Jul 9, 2021

I'm sorry, but I've had to revert the partial fix. QA was worried that the behaviour as implemented would be too much like a bug (since getting past the Materials menu isn't obvious).

@GregValiant GregValiant added Status: Needs Info Needs more information before action can be taken. Status: Stale ⌛ This issue is over a year old. It might be obsolete or just needs a fresh set of eyes labels Nov 19, 2024
@GregValiant
Copy link
Collaborator

Is this still an issue in current Cura versions (5.8.0 and up)? Can this be closed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Info Needs more information before action can be taken. Status: Stale ⌛ This issue is over a year old. It might be obsolete or just needs a fresh set of eyes Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

5 participants