2008-08-16 09:33:06 |
fabb |
bug |
|
|
added bug |
2008-08-16 09:33:06 |
fabb |
bug |
|
|
added attachment 'workspace switcher bug.png' (workspace switcher bug.png) |
2008-08-16 20:06:03 |
Mark Lee |
awn: status |
New |
Incomplete |
|
2008-08-16 20:06:03 |
Mark Lee |
awn: bugtargetdisplayname |
Awn |
Awn Extras |
|
2008-08-16 20:06:03 |
Mark Lee |
awn: bugtargetname |
awn |
awn-extras |
|
2008-08-16 20:06:03 |
Mark Lee |
awn: statusexplanation |
|
Per the instructions on the bug reporting form, this needs to be moved to the Awn Extras bug tracker.
Which window manager are you using?
It should be noted that the "classic" workspace switcher can change its width/height via its preferences dialog (although I think you have to re-activate the applet in order to see the height change). |
|
2008-08-16 20:06:03 |
Mark Lee |
awn: title |
Bug #258525 in Awn: "visual aspect ratio bug with shiny switcher applet" |
Bug #258525 in Awn Extras: "visual aspect ratio bug with shiny switcher applet" |
|
2009-01-04 00:20:12 |
onox |
awn-extras: assignee |
|
rcryderman |
|
2009-01-04 00:20:12 |
onox |
awn-extras: statusexplanation |
Per the instructions on the bug reporting form, this needs to be moved to the Awn Extras bug tracker.
Which window manager are you using?
It should be noted that the "classic" workspace switcher can change its width/height via its preferences dialog (although I think you have to re-activate the applet in order to see the height change). |
|
|
2009-01-05 15:55:20 |
moonbeam |
awn-extras: status |
Incomplete |
Confirmed |
|
2009-02-05 20:57:10 |
onox |
awn-extras: milestone |
|
0.3.2 |
|
2009-02-07 19:40:20 |
moonbeam |
awn-extras: status |
Confirmed |
Fix Committed |
|
2009-02-07 19:40:20 |
moonbeam |
awn-extras: statusexplanation |
|
This should be properly resolved in trunk. If any cases of this can still be reproduced with trunk please reopen the bug |
|
2009-02-09 03:03:13 |
moonbeam |
awn-extras: status |
Fix Committed |
Fix Released |
|
2009-02-09 03:03:13 |
moonbeam |
awn-extras: statusexplanation |
This should be properly resolved in trunk. If any cases of this can still be reproduced with trunk please reopen the bug |
|
|