Ticket #1996 (s2c_design_ok bug) — at Version 6
Ctrl+Shift+Tab should scroll opened books tabs backwards
Reported by: | deyan | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | M12_RELEASE |
Component: | uncategorized | Version: | 2.0 |
Keywords: | feedback | Cc: | |
Category: | unknown | Effort: | |
Importance: | Ticket_group: | ||
Estimated Number of Hours: | 0 | Add Hours to Ticket: | 0 |
Billable?: | yes | Total Hours: | 0 |
Analysis_owners: | deyan, vanya | Design_owners: | nenko |
Imp._owners: | nenko | Test_owners: | |
Analysis_reviewers: | nenko | Changelog: | Changelog |
Design_reviewers: | meddle | Imp._reviewers: | meddle, todor |
Test_reviewers: | Analysis_score: | 1 | |
Design_score: | 1 | Imp._score: | 1 |
Test_score: | 0 |
Description (last modified by vanya) (diff)
See #1975, Ctrl+Tab should scroll book tabs in order of appearence, Ctrl+Shift+Tab should scroll them in the reverse order.
- Create 4 New Books and put focus on the first book
- Press Ctrl+TAB
- Press Ctrl+TAB again
- Press Ctrl+TAB again
- Press Ctrl+TAB again
- The focus is on the first book
- Focus moves to second book
- Focus moves to third book
- Focus moves to second book
- Focus moves to third book
The application doesn't throw an exception and doesn't crash but it doesn't have the expected behaviour. Focus should move to fourth book on step 4 and to the first book on step 5.
Change History
comment:3 Changed 16 years ago by nenko
- Design_owners set to nenko
- Status changed from s1b_analysis_finished to s2a_design_started
- Imp._owners set to nenko
comment:4 Changed 16 years ago by nenko
- Status changed from s2a_design_started to s3b_implementation_finished
comment:5 Changed 16 years ago by meddle
- Status changed from s3b_implementation_finished to s2c_design_ok
- Analysis_reviewers set to nenko
- Analysis_score changed from 0 to 1
- Imp._reviewers set to meddle, todor
- Design_score changed from 0 to 1
- Design_reviewers set to meddle
- Imp._score changed from 0 to 1
The behavior of the shortcuts is not like the defined in the bug's requirements and there is no design section so:
1p
Note: See
TracTickets for help on using
tickets.