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 738923 - get_preferred_height_vfunc in custom CellRenderer not respected after upgrade from 3.12 to 3.14
get_preferred_height_vfunc in custom CellRenderer not respected after upgrade...
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: Other
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2014-10-21 11:25 UTC by Gaute Hope
Modified: 2018-04-15 00:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Gaute Hope 2014-10-21 11:25:39 UTC 
Hi,

I have created a custom CellRenderer in gtkmm. I have overloaded the method:

      virtual void get_preferred_height_vfunc (
          Gtk::Widget& widget,
          int& minimum_height,
          int& natural_height) const override;

and sets minimum_height and natural_height to calculate the height of my cell.

After upgrading gtk+ and gtkmm to 3.14 from 3.12 the value I set using this function no longer has any effect. I do not know whether this is a gtkmm or gtk+ problem.
Comment 1 Gaute Hope 2014-10-26 21:43:13 UTC 
It turns out this was only a problem on my mac book pro with a retina screen (hidpi). When I overloaded the function:

   get_request_mode_vfunc and return CONSTANT_SIZE or HEIGHT_FOR_WIDTH

and also wrap:

   get_preferred_width_vfunc (...)

things work out. The return value of the latter functions seems to be irrelevant. But if I do not wrap it I get an assertion failure upon runtime.

Is this expected behaviour? If so, I could not find any documentation.

Cheers, Gaute
Comment 2 Matthias Clasen 2018-02-10 05:08:23 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 3 Matthias Clasen 2018-04-15 00:31:44 UTC 
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new