IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Stupid but reliable solution
Have the error library have an internal flag for this, which defaults false, but which can be reset.

When the GUI application starts, have it set the flag.

Yeah, yeah, it is a global. So are environment variables. And some day you may have your application called from a process that inherited an environment from an unrelated GUI. (But you are backgrounded.)

Globals which are shared across processes are worse than globals inside of processes...

Cheers,
Ben
New I'm not that doctrinare...
...but I would try to keep globals to a minimum. There is precedent for such a solution in this system, however, so it wouldn't be hard getting it past a code inspection.

Thanks for the input, Ben.
jb4
(Resistance is not futile...)
     Question for all you UNIX masters out there... - (jb4) - (12)
         if you called it cause it is current how come ya dont know? - (boxley) - (4)
             I'm an error library, and I don't know which proc called me - (jb4) - (3)
                 GUI detection - (kmself)
                 Stupid but reliable solution - (ben_tilly) - (1)
                     I'm not that doctrinare... - (jb4)
         Re: Question for all you UNIX masters out there... - (pwhysall) - (3)
             Thank you, but... - (jb4) - (2)
                 Why don't you sneak a look at the source code for ps or top? - (pwhysall) - (1)
                     Good Plan! Hadn't thought of that.... -NT - (jb4)
         Try the environment variable "_" - (lordbeatnik)
         well if yer inside the app - (boxley)
         Here's what I got so far... - (jb4)

Ichi, ni, san, shi.
67 ms