After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 513471 - rounded corners for entries are hard to do
rounded corners for entries are hard to do
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: GtkEntry
2.12.x
Other Linux
: Normal enhancement
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2008-01-31 16:08 UTC by Benjamin Berg
Modified: 2010-10-21 12:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Benjamin Berg 2008-01-31 16:08:03 UTC
GtkEntry and subclasses have two X windows. An inner one with the area of the text, and an outer one which is also filled with the base color. To draw rounded rectangles in themes it is commen to try and get the background color from some source (eg. walking up the widget tree) and filling the background of the outer window first. This works pretty good for normal GTK+ applications, but creates problems if the entry is used on a canvas (or eg. faked in mozilla).

To help with this it would be nice if the second window of the entry would be removed, or made input only. I do not know how feasable this may be (API and implementation wise).

Another solution that I thought about for mozilla is that mozilla attaches some data to the widget (eg. "gtk-engine-hint-transparent-bg") and the engine does not fill the background then. This may also be a feasable temporary workaround if that is desired. (The engines code could just drop the workaround code GTK+ is changed.)
Comment 1 Benjamin Berg 2008-05-29 14:02:40 UTC
Just for the information. It tourned that some Pixmap themes seem to depend on the background to be filled in, so the workaround idea for mozilla does not seem to work well.
Comment 2 Martin Sourada 2010-08-05 16:59:40 UTC
Any chance this (and Bug 513476) gets fixed in gtk3?
Comment 3 Matthias Clasen 2010-10-21 12:57:47 UTC
Should be much easier now.