Re: [gtk-osx-users] gtk+3.10 on MacOSX 10.8.5 with Retina display




On Oct 10, 2013, at 12:55 AM, Andrius <andriusr yahoo com> wrote:

Hi all,
I just upgraded to latest module set that uses gtk+3.10 and gtk-mac-integration 2.0.4. My computer has Retina display, I guess most of the issues described below are related to Retina. I am building bluefish from svn depository. The build was successful, I created bundle the same way I did for gtk+3.6.4.
1. In the log file when bluefish was started there is line
(bluefish-bin:55298): Gtk-WARNING **: unsupported GDK backend.
Probably this means that quartz is no longer supported?
2. The icons in the toolbar are HUGE. The linear dimensions probably got 2 times larger than before (so, area is 4 times larger). It seems that this is caused by depreciation of gtk-toolbar-icon-size from Settings. In older version this setting was affecting icon size together with gtk_toolbar_set_icon_size(); if I set smaller icon size in Settings, the icons Now even smallest icon set is way too large for my screen.
3. The interface inself looks to be out of proportions. Notebook tabs are much larger, the same for combobox, some icons does not fits into place and so on. Its complete mess.
4. The fonts in GtkTextView and GtkTreeView are blurred. In older version I was able to fix it by putting into bundles Info.plist the lines
<key>NSHighResolutionCapable</key>
<true/>
But now this does not work anymore - no effect at all.

There's supposed to be support for HiDPI in 3.10, but I haven't looked at the commits, so it might not have been implemented in quartz. Details in
The last one suggests that a build from cairo-git might fix it. A build with the unstable modulesets will get you that.

5. There is issue also with gtk-mac-integration. When creating new window sometimes bf crashes with log looking like this:

Can you call setup_debug() in .jhbuildrc-custom and rebuild gtk-mac-integration, then crash it again so I can see the line number in cocoa_menu_item_add_submenu is trying to remove the not-added menu item? Even better, of course, would be to debug the crash and tell me why that menu item is getting removed when it shouldn't.

I only need that stack frame, not the whole report.

This issue was not present in 2.0.1.
Well, I hope that there is fix for all these things, but my guess is that this will not be an easy task...
Any ideas?


Regards,
John Ralls





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]