Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Message-ID: <39650375.29FD66FD@cygnus.com> Date: Fri, 07 Jul 2000 00:08:53 +0200 From: Corinna Vinschen Reply-To: cygdev X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.14-SMP i686) X-Accept-Language: de, en MIME-Version: 1.0 To: cygdev Subject: Re: experimental new GUI setup References: <200007061736 DOT NAA21944 AT envy DOT delorie DOT com> <20000706154444 DOT A22109 AT cygnus DOT com> <200007061954 DOT PAA05193 AT envy DOT delorie DOT com> <3964EAC0 DOT 23BA1498 AT cygnus DOT com> <200007062038 DOT QAA05534 AT envy DOT delorie DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit DJ Delorie wrote: > > > SystemParametersInfo(SPI_GETFOREGROUNDLOCKTIMEOUT, 0, 0, 0); > > Does this disable it for the whole system, or just the current > application? It's a parameter changing system behaviour. You can use the DWORD timeout; SystemParametersInfo(SPI_GETFOREGROUNDLOCKTIMEOUT, 0, &timeout, 0); call to get the old param and reset it to the old value when your setup has finished. Note that only the current foreground application can change that parameter. You can avoid that by starting the other application/thread which opens the error box explicitly as the foreground application (Create a window, call SetForegroundWindow()). You may do this, because you're started from the previous foreground application. Note that _any_ user intervention (eg. clicking on a window of some other application) prevents your error box from being in the foreground. That's W2K, the M$ crew seems to be very happy about that new feature, but... don't ask me! Corinna