[Bug 12054] New: Bug on GTK Human-Theme

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Tue Jun 21 09:28:15 UTC 2005


Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=12054
Ubuntu | ubuntu-artwork

           Summary: Bug on GTK Human-Theme
           Product: Ubuntu
           Version: unspecified
          Platform: i386
        OS/Version: other
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ubuntu-artwork
        AssignedTo: jeff.waugh at ubuntu.com
        ReportedBy: thesaltydog at gmail.com
         QAContact: desktop-bugs at lists.ubuntu.com


This is the problem:
Download the cellrenderer_progress example in cvs:
http://cvs.sourceforge.net/viewcvs.py/gtk2-perl/gtk2-perl-xs/Gtk2/examples/cellrenderer_progress.pl?rev=1.1&view=log

If you run the program you will get a long list of:
GLib-GObject-WARNING **: invalid cast from `GtkTreeView' to `GtkRange'
at ./cellrender_progress.pl line 87.

I didn't make any adaptation. Line 87 of the code is:

 $style->paint_box ($window,
                   'normal', 'in',
                   undef, $widget, "trough",
                   $cell_area->x + $x_offset + $xpad,
                   $cell_area->y + $y_offset + $ypad,
                   $width - 1, $height - 1);

Human theme is claiming for a GtkRang, that is NEVER used in the sample program.
Neither the code in GTK+ nor the code in the example deal with a GtkRange, yet
somebody in the pipe, starting from a style method, is complaining about a bad
cast.

The widget parameter to paint_box() is used by the theme implementation to get
hints, either from style properties or from the type of the object itself.
The "what sort of box" hint is the string "trough", and my guess is that your
theme's implementation of paint_box() thinks that a "trough" will only be
drawn for a GtkRange.

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the desktop-bugs mailing list