No, this is definetly not a Gtk# bug. Gtk# only pinvokes Gtk+ functions; the behavior of the application is determined entirely by Gtk+.
Well as that bug was fixed in 2.13.x replacing all the Gtk+ files shipped with Gtk# should solve your problem. Did you really override the Gtk+ files? Just installing Gtk+ could cause Gtk# to stick to the old version. You need to use the Gtk+ bundle from http://www.gtk.org/download-windows.html and override all the files. If it still doesn't work, you should write a mail to the gtk+ lists. Christian Philip Wobst wrote: > Hi Christian and others, > > Thanks for your feedback. I have tried the approach you suggested but > updating the Gtk+ files does not fix the issue. This applies to the > following environment: > > 1. Windows XP Home SP 3 > 2. Mono 2.2 install > 3. Replace all the files that were installed by the Gtk+ 2.16 installer > found on http://gtk-win.sourceforge.net/home/index.php/en/Home > > I have also tested this bug on the Linux Mono VMWare machine and there > the bug does not turn up (Gtk version 2.12). Could this be a gtk# bug > instead? > > All help or suggestions is appreciated. > > Regards, > > Philip > > _______________________________________________ Gtk-sharp-list maillist - Gtk-sharp-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/gtk-sharp-list
