From: Daniel P. B. <ber...@re...> - 2007-08-31 20:26:14
|
On Wed, Aug 22, 2007 at 04:58:17PM +0100, Daniel P. Berrange wrote: > On Wed, Aug 22, 2007 at 05:43:43PM +0200, Gerd Hoffmann wrote: > > >> Also vnc_display_open(), vnc_display_close(), then again > > >> vnc_display_open() with the same widget instance doesn't work. > > > > > > Do you call the vnc_display_close & vnc_display_open immediately following > > > each other, or does the mainloop run ? The close function does an asynchronous > > > shutdown so the GTK mainloop needs to run before it'll actually die off. > > > > mainloop runs inbetween due to user interaction being needed (there is a > > "connect ..." menu entry). > > Ok that's odd - is your client app code around anywhere public to test with ? I've pushed a couple of changes which should fix the shutdown problems. Not nearly enough of our read calls were interruptable & there were a few places where we forgot to check has_error. Let me know if there are still problems with closing & re-opening.... Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| |