View Issue Details

IDProjectCategoryView StatusLast Update
0003967ardourbugspublic2020-04-19 20:15
Reporterbmdaugherty Assigned Tocth103  
PrioritynormalSeveritytrivialReproducibilityalways
Status closedResolutionfixed 
Product Version3.0-alpha4 
Target Version3.0 
Summary0003967: Inconsistent user interface elements in editor window.
DescriptionSome buttons such as editing tools and 'sound notes' do not have borders, while others like 'edit region contents' and 'panic' do. This is visually confusing, especially given the current grouping of said buttons.
TagsNo tags attached.

Activities

cth103

2011-04-16 11:03

administrator   ~0010563

Fixed in SVN 9355.

oofus

2011-04-16 16:32

developer   ~0010568

Also, some buttons still have pre-light, whereas others don't. No pre-light is the preferred option.

cth103

2011-04-17 02:17

administrator   ~0010569

What's the reason for preferring no pre-light?

oofus

2011-04-17 08:04

developer   ~0010570

History: There were lots of buttons that were difficult to use because of pre-light. The mouse would hover over the button which would pre-light, the user clicked the button but because of the pre-light wouldn't then show its status. Then when the mouse cursor was moved away from the button the button would show its status (on/off colour). This was most obvious and annoying on things like solo mute and rec arm. So, Paul implemented a new button type (as I understand it) that only has an on and off colour state and no other colouring what so ever. This gives a far more consistent look and feel and is far less confusing in operation. For consistency 'all' buttons should be like this; there are still a few in both the editor and mixer that don't quite conform to this.

bmdaugherty

2011-04-17 17:10

reporter   ~0010573

I agree. I was going to file a separate bug report for the pre-light, but didn't know exactly how to explain myself. Well done. Thanks.

cth103

2011-12-13 00:26

administrator   ~0012399

Is this still an issue with the new button stuff?

cth103

2012-03-03 23:49

administrator   ~0012841

I believe this is fixed with the new button code; please re-open the bug if you still have problems.

system

2020-04-19 20:15

developer   ~0022535

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2011-04-12 16:20 bmdaugherty New Issue
2011-04-12 18:14 cth103 cost => 0.00
2011-04-12 18:14 cth103 Target Version => 3.0-beta1
2011-04-16 11:03 cth103 Note Added: 0010563
2011-04-16 11:03 cth103 Status new => resolved
2011-04-16 11:03 cth103 Resolution open => fixed
2011-04-16 11:03 cth103 Assigned To => cth103
2011-04-16 16:32 oofus Note Added: 0010568
2011-04-16 16:32 oofus Status resolved => feedback
2011-04-16 16:32 oofus Resolution fixed => reopened
2011-04-17 02:17 cth103 Note Added: 0010569
2011-04-17 08:04 oofus Note Added: 0010570
2011-04-17 17:10 bmdaugherty Note Added: 0010573
2011-11-15 17:20 cth103 Target Version 3.0-beta1 => 3.0-beta2
2011-12-13 00:26 cth103 Note Added: 0012399
2012-01-10 20:45 cth103 Target Version 3.0-beta2 => 3.0-beta3
2012-02-14 17:20 paul Target Version 3.0-beta3 => 3.0 beta4
2012-03-03 23:49 cth103 Note Added: 0012841
2012-03-03 23:49 cth103 Status feedback => resolved
2012-03-03 23:49 cth103 Resolution reopened => fixed
2012-05-23 15:09 cth103 Target Version 3.0 beta4 => 3.0
2020-04-19 20:15 system Note Added: 0022535
2020-04-19 20:15 system Status resolved => closed