Make the Alt-tab explode timer count from when the frame was dislayed, not when it happened
Bug #856520 reported by
Paul Sladen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ayatana Design |
Invalid
|
Undecided
|
Unassigned | ||
| Unity |
Invalid
|
Undecided
|
Unassigned | ||
| unity (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
In the alt-tab switcher the latency of the Alt-tab switcher frame rate gets quite close to the Alt-tab expanding exploder time out.
This means that if you wait until to see which icons is actually highlighted that icon could have exploded into a set of window previews by the time it the seen has seen it.
Ideally the exploder timer should be tied to the point at which the frame was displayed. This can be approximated by adding on the current inverse of the current framerate. This would mean that the user always has a consistent and predictable reaction time ceiling, rather than having to keep alt-tabbing ahead just to stop the window display exploding on the off-chance that the current FPS is low.
| Changed in unity: | |
| status: | New → Incomplete |
| Changed in unity (Ubuntu): | |
| status: | New → Incomplete |
| Changed in unity: | |
| status: | Incomplete → New |
| Changed in unity (Ubuntu): | |
| status: | Incomplete → New |
Revision history for this message
| Andrea Azzarone (azzar1) wrote | #1 |
| Changed in ayatana-design: | |
| status: | New → Incomplete |
| Changed in unity: | |
| status: | New → Invalid |
| Changed in ayatana-design: | |
| status: | Incomplete → Invalid |
| Changed in unity (Ubuntu): | |
| status: | New → Invalid |
To post a comment you must log in.
Alt-tab is faster in most recent unity versions. Please reopen it if you can still reproduce the bug.