Missing mechanism in Glibmm that prevents the support of some themes (CSS) in Gtkmm

Bug #1846699 reported by Alejandro Claro on 2019-10-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
glibmm2.4 (Ubuntu)
Undecided
Unassigned

Bug Description

In GTK+ 3.20 the theming mechanics was heavily changed.

https://developer.gnome.org/gtk3/stable/ch32s10.html

One of the major changes was the use of element names much more than style classes. For this the function gtk_widget_class_set_css_name() was added to t he API and used to assign the element names. However, this was not added in GTKmm, making impossible to assign element names in custom widget, and no automatically assignment was developed in GTKmm's Widget class in order to be able to identify widget classes in the theming system (CSS).

The problem was discussed and tracked up to Glibmm in GNOME bug tracking system:

https://gitlab.gnome.org/GNOME/gtkmm/issues/17
https://gitlab.gnome.org/GNOME/glibmm/issues/33

The issues are due to the lack of the mechanism to call gtk_widget_class_set_css_name() function in the instance init function.

This was solved in Glibmm2.4 2.60, however Ubuntu is still behind this version and it's affecting some of our products.

We have applied a patch to the current version (2.56) of Glibmm2.4 in Ubuntu 18.04 successfully, but I would like to ask you to consider upgrading the version of Glibmm in the official repository or apply the patch.

Alejandro Claro (aclaro) on 2019-10-04
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers