Comment 38 for bug 792115

Revision history for this message
su_v (suv-lp) wrote :

With r10794 I get erratic, partially broken behavior on darwin with Inkscape's dockable dialogs:

A - Old (stable) 32bit build env (Mac OS X 10.5.8 (i386), Xcode 3.1.4):
glib2 2.28.8, gtk+/x11 2.24.4 and gtk+/quartz 2.24.8, gtkmm 2.24.0 gcc 4.2.1

1) optimized builds (-O3) seem to be ok
(both backends of gtk tested: x11 and quartz)

2) debug build (-g -O0) broken:
none of the dockable dialogs opens at all (not when clicking on a button, nor when using the menu command nor with keyboard shortcuts)

B - New (work-in-progress) 64bit build env (OS X 10.7.2 (x86_64), Xcode 4.2.1):
glib2 2.30.2, gtk+/x11 2.24.8, gtkmm 2.24.2, llvm-gcc-4.2

1) optimized builds ('-03', '-O2') show erratic behavior:
A random test string (apparently from the translatable messages) is output to the console when launching inkscape, and each time a docked or detached dockable dialog is closed, these kind of warnings from GDL are generated:
** (inkscape:12782): WARNING **: Something weird happened while getting the child placement for 0x7f8756408350 from parent 0x7f87554ffb20

2) debug build: works seemingly fine (but slow).
no random text output nor warnings when closing dockable dialogs.

(tested with default gtk theme (Raleigh), and default inkscape prefs,
 last tested prior revision: 10785 on 10.5.8, 10788 on 10.7.2)