Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 16 Apr 2004 13:12:17 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygwin setup window size, why no maximize button enabled ? Message-ID: <20040416171217.GA10313@coe.bosbc.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20040416152356 DOT GA8008 AT coe DOT bosbc DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Fri, Apr 16, 2004 at 05:45:33PM +0100, Dave Korn wrote: >cgf writes: >>I've been advocating just releasing the current snapshot as is, > >It's a judgement call, so AFAICS it's largely just a matter of taste. >A buggy GUI is not the end of the world and if a user gets it into an >unworkable state all they need do is cancel and start again. But now we have a buggy GUI which is guaranteed to be in an unworkable state. The current implementation is pretty user-unfriendly. It boils down to a lesser of two evils. >OTOH it looks kind of flaky for a release. It's about image and >presentation and neat-and-tidy-ness. I suppose there's no reason not >to release it and list the gui problems as known bugs, PTC. I've just >been doing some MFC coding for the first time, I'll take a look at >fixing some bugs when[*] I get some spare time. Help would be appreciated but setup doesn't use MFC. >>although it would also be nice to fix the pcre0 dependency problem. > >Can't speak to the dependency problem, as I haven't run up against it, >but I remember seeing a lot of posts on the list from people who've not >had libpcre0 properly installed until they re-run setup a second time; >do you mean that it's a bug in setup's algorithm that it doesn't >properly calculate the dependency of various packages that use it on >the library, rather than some issue to do with the packaging/setup hint >files? It's a setup algorithm problem. I can't think of any way to write a setup.hint file such that dependencies don't show up in the first setup run but do show up in the second run. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/