[gtk3] Histogram visual nits
Submitted by Jim Nelson
Assigned to Lucas Beeler
Link to original bug (#717755)
Description
---- Reported by jim@yorba.org 2011-07-22 15:41:00 -0700 ----
Original Redmine bug id: 3869
Original URL: http://redmine.yorba.org/issues/3869
Searchable id: yorba-bug-3869
Original author: Jim Nelson
Original description:
The change from Gtk.Style -> Gtk.StyleContext requires that the histogram be drawn differently under GTK 3. For some reason, the obvious replacement calls are not working and so only the histogram chart and the nubs (barely) are seen.
Related issues:
- related to shotwell - 3658: The histogram sliders are inappropriately visible when th... (Open)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:39:00 -0700 ----
History
Comment 1
Updated by Adam Dingle about 2 years ago
- Target version set to 0.12
Comment 2
Updated by Adam Dingle about 2 years ago
- Priority changed from Normal to High
Comment 3
Updated by Lucas Beeler about 2 years ago
- Subject changed from [gtk3] Histogram not drawn correctly to [gtk3] Histogram visual nits
- Description updated (diff)
This has been mostly fixed in 2c79d059. The histogram control is now fully usable again. There are some remaining visual nits (e.g, the theme engine isn't properly drawing the slider trough and frame bevel), but they involve deep theme-based widget rendering code. I'm in communication with the GTK+ 3 guys about it.
Comment 4
Updated by Lucas Beeler about 2 years ago
- Status changed from Open to 5
- Assignee set to Lucas Beeler
- Resolution set to fixed
Fixed in ad51e8fe
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:53 UTC ---
This bug was previously known as bug 3869 at http://redmine.yorba.org/show_bug.cgi?id=3869
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.12
Resolution: RESOLVED FIXED