Carsten Haitzler (The Rasterman) wrote:
On Fri, 28 Oct 2005 12:28:34 +0200 Sebastian Dransfeld <[EMAIL PROTECTED]>
babbled:
enlightenment-cvs@lists.sourceforge.net wrote:
Enlightenment CVS committal
Author : raster
Project : e17
Module : apps/e
Dir : e17/apps/e/src/bin
Modified Files:
e_hints.c e_main.c
Log Message:
actually rather pointless to unset over there. unset at startup :)
Nope. The previous was correct. The problem is that DESKTOP_STARTUP_ID
is exported to the system, so you can access it from a shell. So any
application launched from a shell after a .eap is launched from E will
get this startup id.
um - but thats how its supposed to work. the environemtn variable is exported
to the sub process being forked - it then gets its own copy in the child
process and thus eventually the execced process - the execced process uses this
env var to set properties on its window. it is the job of this sub process then
to unset the env var before execcing anythng else itself :) ie - thw whole
POINT of this var IS to export it to executed apps :)
Damn, I'm braindead. The point is when a process doesn't know anything
about the startup id stuff, and doesn't unset the env. So my fix was
faulty too. There should be something to identify an exe'd process and
unset the env variable if the process doesn't. A pid check and a timer?
Sebastian
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
