Re: [java-gnome-hackers] Ugly deadlock with Dialog.run()

[Andrew C. <an...@op...>]

On Tue, 2010-08-10 at 15:46 +0200, Vreixo Formoso wrote:
> > 1. Take our own lock (which we could then manually unlock in special
> > cases)
> > 
> > 2. Just mess with a manual MonitorExit/MonitorEnter
> > 
> > 3. Seriously mess with the entire main loop process:
> > 

Or maybe

4. Write our own run()

Just a thought I had talking with Guillaume earlier today: we could
maybe just write a run() method in Dialog that does the workaround. ie,
rather than making the developer connect to Dialog.Response, do so
inside run() ourselves. As a convenience.

The trick would be getting that method to block. The only way I could
see to do that would be to nest a call to Gtk.main()... which might
bring us back to the same problem.

AfC
Sydney