adjust pressed button color dynamically to match background
Submitted by Adam Dingle
Assigned to Lucas Beeler
Link to original bug (#717420)
Description
---- Reported by adam@yorba.org 2011-03-01 15:27:00 -0800 ----
Original Redmine bug id: 3276
Original URL: http://redmine.yorba.org/issues/3276
Searchable id: yorba-bug-3276
Original author: Adam Dingle
Original description:
When a search toolbar button is pressed in, its background color is slightly darker than the surrounding dark gray, but it's still not as obviously noticeable as it should be. We should try to make the pressed buttons more distinct, either by varying the background color more or by moving to a different button style such as a flat button.
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:39:00 -0700 ----
History
Comment 1
Updated by Adam Dingle over 2 years ago
- Status changed from Open to Review
- Assignee changed from Anonymous to Lucas Beeler
Comment 2
Updated by Adam Dingle over 2 years ago
- Subject changed from search toolbar buttons aren't distinct enough when pressed to adjust pressed button color dynamically to match background
The color of pressed buttons currently stays constant as the user changes the background color. We should change it on the fly, dynamically choosing a color that contrasts reasonably with the background color.
Comment 3
Updated by Adam Dingle over 2 years ago
Turns out this is hard, so we've decided to update the button background color only when the user closes the Preferences dialog. Not ideal, but we'll live with this for 0.9.
Comment 4
Updated by Lucas Beeler over 2 years ago
- Status changed from Review to 5
- Resolution set to fixed
- % Done changed from 0 to 100
r2751
Comment 5
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:51 UTC ---
This bug was previously known as bug 3276 at http://redmine.yorba.org/show_bug.cgi?id=3276
Unknown Component Using default product and component set in Parameters Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Version: 0.9
Resolution: RESOLVED FIXED