> > Gedit was only an example of how a single process can manage different > windows, not of how a single process can receive new calls from it being > executed (because gedit does that through DBus, which is not a solution > for you). > > But once you switch to the "one process, any number of windows" > principle, then _that_ single process can spawn, with multiprocessing, > its server, stuck listening, and any new process will just tell _that_ > server what to open, and then would die in peace. > > For instance, currently when I ask CherryTree to create a new instance, > the currently open one is closed. Instead, the app could open it in a > new window. Being able to do something like that that doesn't solve the > problem of the communication with new processes independently spawned, > but seems to me a first step. > > Pietro
I finally succeeded with the principle you adviced "one process, any number of windows", adding just one thread that acts as the server. Many thanks you for the help, best regards, Giuseppe.
_______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
