X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <4A7693E9.6030100@openttcn.fi> Date: Mon, 03 Aug 2009 10:38:17 +0300 From: Arne Pajunen User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Setup maximizing package explorer Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Hey, I've been using the 1.7 releases and they're quite nice. However, I've been noticing a minor inconvenience with the new setup: It maximizes to fullscreen when entering the package explorer. I'm sure this is a nice feature on smaller monitors where people often run programs maximized, but for those using larger resolutions like 1920x1200 it just creates lots of useless white area on the screen, and on a 30" 2560x1600 resolution 95% of the screen is covered in white which seems kind of excessive. My suggestion would be to do one of the following: 1. Don't maximize, let user choose if he wants his programs fullscreen by doing it themselves. 2. Make the maximization conditional and only do it for small display resolutions. 3. Add a checkbox that is remembered between runs so the user can state their preference. Would be nice to see one of these implemented, even if it's just a minor inconvenience to un-maximize every time running the setup. Best Regards, Arne Pajunen -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple