[Gtk-sharp-list] Can't click button after dialog closes

[Philip Wobst]

Hi Christian,

Thanks for your feedback. On my test system I made sure, that the only file left is the libgtk-win32-2.0-0.dll with the new version. And on my devolopment machine the version is 2.14.7 and on both systems I have the issue. It might turn out to be something totally different. The Gtk+ version on the vmware image is 2.12.9 and the issue does not occur.
Maybe this is something different that came up in a later release of gtk+ and is not related to the bug I originally found! I will try to test with an older version on Windows and with a newer version on the vmware image now.

Thanks and reagrds,

Philip
-----Ursprüngliche Nachricht-----
Von: Christian Hoff [mailto:christian_hoff at gmx.net] 
Gesendet: Donnerstag, 9. April 2009 13:15
An: Philip Wobst
Cc: gtk-sharp-list at lists.ximian.com
Betreff: Re: AW: [Gtk-sharp-list] Can't click button after dialog closes

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
>
>