On Sun, 2017-05-07 at 19:52 +0000, Emmanuele Bassi wrote:
> 
> On Sun, 7 May 2017 at 19:53, Richard Shann <rich...@rshann.plus.com>
> wrote:
> 
>         On Sun, 2017-05-07 at 17:54 +0100, Emmanuele Bassi wrote:
>         > On 7 May 2017 at 16:52, Richard Shann
>         <rich...@rshann.plus.com> wrote:
>         > > I have a test program that pops up a label with a
>         customized
>         > background
>         > > and foreground color. This works in 3.12 using the syntax
>         > >
>         > > "GtkLabel {background-color: #FFFF00;}"
>         > >
>         > > and
>         > >
>         > > "GtkLabel {color: #FF00FF;}"
>         > >
>         > > but fails in 3.22
>         >
>         > The selector for labels is "label" since GTK+ 3.20.
>         
>         Thank you very much for this. Is there a function to get the
>         selector
>         for a widget? Sort of gchar *gtk_widget_get_css_selector
>         (GtkWidget *w)
>         thing? 
> 
> 
> I'm not sure what would that accomplish. Could you elaborate?

It would enable my program to work. Currently it gets the string
"GtkLabel" from the type name of the widget, and that works for setting
the background color of various widgets in the program, replacing
deprecated calls.
> 
> 
>         Looking through a few widgets it seems the rule is chop off
>         the
>         Gtk prefix and lower case what remains ... is that guaranteed?
> 
> 
> No, it's not. It's part of the API reference for a reason.
> 
> If somebody creates a custom widget, with a custom CSS element name,
> then they will have to document it.
> 
yes, but surely there is no harm in you documenting what you do with the
widgets that come with Gtk in order to create a selector name? Otherwise
a) we have to look it up each time
b) we can't create it programmatically for programs like the one I
posted.

Richard

> 


_______________________________________________
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list

Reply via email to