After hitting "send" with John's answer I saw Matthias question. So here is my
next answer:
Yes, it is a daemon "a la carte". It forks, os.setsid, forks, redirects
sys.stdin and sys.stdout to /dev/null. The code resides in /etc/init.d and
dependencies are taken care of.
But I don't think this should be a problem because the following works from the
Python
prompt, as root, in screen 1, targeting screen 7 (where my KDE loads) which is
under
<regular user> control:
<code>
>>> import sys
>>> from Tkinter import *
>>> sys.stdout=open('/dev/null','w')
>>> r=Tk(screenName=':0.0')
>>> Label(r,text='Gutten Tag!').grid()
</code>
My daemon does all kind of other things, and it does them well; my only issue
is when I have to
break its silence and inform the user, in GUI, about issues that (s)he may need
to take action.
My preferred approach was the one described here, my alternative was the
dettached Toplevel
described in my first posting; I can't make none to work.
Thanks for suggestions,
Sorin
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com _______________________________________________
Tkinter-discuss mailing list
[email protected]
http://mail.python.org/mailman/listinfo/tkinter-discuss
