Thanks for the suggestions, Emmanuele! I will try them. - Weihua
2009/11/30 Emmanuele Bassi <[email protected]>: > Hi; > > > >> Currently my program only has one thread. First I thought if I can do a >> nested call of clutter_main so the thread can be blocked untill the dialog >> finishes its job. But it's failed and the problem is hung at the >> clutter_main. I don't know why? > > > > Yes, there is a known issue, that I haven’t had time to properly debug, with > nested main loops. There is bug 1018 opened about this. > > > >> Then I thought if I can create another thread to handle the dialog stuff >> and block the main thread untill the dialog return. I have not tried that >> yet. > > > > Don’t mix threads and main loops, and don’t access the Clutter API from > different threads *ever* > > > >> I think such usage model should be common and there are must be some >> existing solutions. > > > > It might be common for a desktop toolkit – but Clutter is not a desktop > toolkit. > > > >> Can anyone help to provide any suggestion? Thanks in advance! > > > > Use clutter-gtk and the GTK+ API to raise a dialog window. > > > > Ciao, > > Emmanuele. > > -- To unsubscribe send a mail to [email protected]
