Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
gtk
gtk
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,125
    • Issues 1,125
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 149
    • Merge Requests 149
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GNOME
  • gtkgtk
  • Issues
  • #659

Closed
Open
Opened Aug 21, 2016 by bugzilla-migration@bugzilla-migrationReporter

Changing the visibility of GtkToolBar contents causes allocation warnings

Submitted by Kai Willadsen @kaiw

Link to original bug (#770182)

Description

Created attachment 333780 Simple python test case

Reproduced against the current 3.20.x branch HEAD. This is a new regression as of GTK+ 3.20.

The attached test case just shows a GtkToolButton in an idle handler, which triggers the following warning:

(toolbar-item-size.py:23245): Gtk-WARNING **: Allocating size to GtkToolButton 0x55f514e1c270 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

There's no visible effect of this on the rendering of the toolbar or its items that I've noticed.

However, there is a more serious side-effect, which is that it (somehow, I have no idea how) causes some GtkRange manipulations in a container with a shared GtkGrid parent to do the wrong thing. I do appreciate how bizarre this sounds. My test case is to trigger this warning in Meld and then see GtkTextView.scroll_to_mark() calls silently fail to actually scroll the mark on-screen.

Attachment 333780, "Simple python test case":
toolbar-item-size.py

Version: 3.20.x

See also

  • Bug 770184
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: GNOME/gtk#659