www.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2000/11/29/19:56:03

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Subject: RE: Two solutions for setup.exe windows hiding
MIME-Version: 1.0
Date: Thu, 30 Nov 2000 11:52:02 +1100
content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.0.4368.4
Message-ID: <188CAABFF1C6AD4D946FF2170CD8B7AA64E2@itdomain002.itdomain.net.au>
Thread-Topic: Two solutions for setup.exe windows hiding
Thread-Index: AcBaZIyCUHOz/VbtQG6yIdCqJkz2zAAAu2qQ
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin AT sources DOT redhat DOT com>
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id TAA16678

Just my 2c...

I really dislike dialogs from windows in the background popping in front
of my current active window. Certainly when the product is launched
coming to the front makes sense. But I'll typically start the download,
switch to another windows and then switch back later to see where it is.
I often end up cancelling dialogs that pop up - because I happened to
hit SPACE or RETURN at the critical time anyway...

so from the look of your solutions I prefer 1.

Rob

> -----Original Message-----
> From: Evan McLean [mailto:ev AT deathsdoor DOT com]
> Sent: Thursday, 30 November 2000 11:31 AM
> To: cygwin AT sources DOT redhat DOT com
> Subject: Two solutions for setup.exe windows hiding
> 
> 
> Hi,
> 
> I have two different solutions to the problem of windows in Setup.exe 
> dropping behind other windows in the Z order that I had reported here 
> recently 
> (<http://sources.redhat.com/ml/cygwin/2000-11/msg00810.html>).
> 
> I can't really see much by the way of pros or cons for the 
> two different 
> solutions so thought I'd outline and see what peoples preferences are.
> 
> SOLUTION 1:
> 
> In main.cc, create an invisable parent window using the 
> CreateWindow API 
> call for the application.  Then all dialogs specify this as 
> there parent 
> window in DialogBox and CreateDialog calls.
> 
> SOLUTION 2:
> 
> In the message processing loop for each dialog, in the switch 
> statement 
> underneath the case for WM_INITDIALOG the following code is added:
> 
> 	case WM_SHOWWINDOW:
> 	  SetForegroundWindow(h);
> 	  return FALSE;
> 
> Either way seems to do the trick with no other impact.  Pros and cons?
> 
> I can provide patches for either for review if anybody wants this.
> 
> Planned other setup enhancements:
> - Cache mirrors.lst.  Only reloads if more than three days 
> old or refresh 
> button clicked.
> - File download resume.  Know how to do it for all except the 
> NetIO_IE5 
> object, so any pointers for that gratefully accepted.  Also: 
> Any problems 
> arise if NetIO_HTTP uses HTTP/1.1 instead of HTTP/1.0?
> 
> E.
> 
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
> 
> 

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019