User:Humitos/PyGObjectIssues

Here are listed all the bugs that we fund into PyGObject while we were porting activities to Gtk3:

• DPI fonts in PangoCairo: https://bugzilla.gnome.org/show_bug.cgi?id=680663
  • Daniel, Martin and I were working on this and Martin told me about trying 133 as the "magic" dpi number. It worked, but Daniel told us that it's not the right way to move on. So we are trying to change the way that we were creating the Pango Layout using:

cr = drawable.get_window().cairo_create()
drawable.create_pango_layout(cairo_context)

instead of:

cr = drawable.get_window().cairo_create()
pango_layout = PangoCairo.create_layout(cr)

I'm not sure if this is definetly solution.

• Reading an image from XPM data: https://bugzilla.gnome.org/show_bug.cgi?id=651962
• GtkTreeModelSort: https://bugzilla.gnome.org/show_bug.cgi?id=680009
• GtkTextIter: https://bugzilla.gnome.org/show_bug.cgi?id=680597
• Insert a GtkTreeView column with attributes: https://bugzilla.gnome.org/show_bug.cgi?id=679415
• Vte.get_text https://bugzilla.gnome.org/show_bug.cgi?id=676999 | https://bugzilla.gnome.org/show_bug.cgi?id=677000
• Webkit: Double scrollbar in Google Apps: https://bugzilla.gnome.org/show_bug.cgi?id=676982
• It's already solved but it is not applied on my F17 package (I think): https://bugzilla.gnome.org/show_bug.cgi?id=674968