Bug 149806

Summary: tab order in timezone dialog not what i expected
Product: [openSUSE] SUSE Linux 10.1 Reporter: Seth R Arnold <seth.arnold>
Component: InstallationAssignee: Stefan Hundhammer <shundhammer>
Status: RESOLVED INVALID QA Contact: Klaus Kämpf <kkaempf>
Severity: Enhancement    
Priority: P5 - None CC: ke, suse-beta
Version: Beta 3   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Development Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Seth R Arnold 2006-02-09 23:31:07 UTC
I like to do configuration of my test machines by keyboard; the timezone configuration screen has a tab order that I wasn't expecting. I would like the tab order to go from large geographical region to timezones within the region. Currently, hitting 'tab' when the geographical regions pane is selected, focus will go elsewhere. (Sorry, I've forgotten where.)
Comment 1 Jiří Suchomel 2006-03-01 07:28:53 UTC
I don't know if the tab order can be defined from ycp. Stefan?
Comment 2 Stefan Hundhammer 2006-03-01 10:20:50 UTC
No. Since the YaST2 UI is a generic toolkit, it has no way of knowing any other reasonable tab order than the default, and for that we rely on what Qt does for us. Qt will typically order them by position - top to bottom, left to right.

For anything else we would have to come up with a brand-new API and explicitly set it from the YCP code. There would have to be a fallback behaviour: What about widgets that are not covered by the explicit setting from that to-be-created call? They have to be integrated into the tab order somehow.

But on the other hand, this is why we lay so much emphasis on keyboard shortcuts: Most widgets have a label, and the UI engine makes sure every single one of them gets a keyboard shortcut assigned as long as this is possible (only [a-z] and [0-9] are eligible for that).

Bottom line: No can do.
Comment 3 Karl Eichwalder 2006-08-09 14:32:32 UTC
*** Bug 198103 has been marked as a duplicate of this bug. ***
Comment 4 Karl Eichwalder 2006-08-09 14:34:21 UTC
Is invisible grouping possible?
Comment 5 Jiří Suchomel 2006-08-09 14:40:22 UTC
*** Bug 197828 has been marked as a duplicate of this bug. ***
Comment 6 Stefan Hundhammer 2006-08-15 16:03:48 UTC
(In reply to comment #4)
> Is invisible grouping possible?

No. See also comment #2.