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: Mon, 30 Aug 2004 11:45:09 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Error creating dialog(update)... Message-ID: <20040830154509.GO8900@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <001301c48ea6$18f066e0$0f0e0d0c AT nb0> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001301c48ea6$18f066e0$0f0e0d0c@nb0> User-Agent: Mutt/1.4.1i Note-from-DJ: This may be spam On Mon, Aug 30, 2004 at 07:29:05PM +0400, Turbanov Vladislav Dmitrievich wrote: >There is a problem while creating a dialog.... The DialogBox Procedure >returns -1,but the GetLastError returns ERROR_SUCCESS... > >While debuging I noticed that it send these messages to DialogProc: 2 >and 130 both of them are not WM_INITDIALOG since it is 272 You seem to be working under the impression that "cygwin" has very basic problems with common windows constructs... It is unlikely that "cygwin" would have problems like this... It is much more likely that the problem is in your own code... Sending email messages to a mailing list is not the way to track down problems... Inspecting your code for errors, adding debugging statements, creating simple test cases for verification, and running it under a debugger is how the vast majority of programmers track down problems... Please don't spam this list every time you have a coding error... Creating dialogs using DialogBox is also not a cygwin-specific problem so this is marginally off-topic and, if you really need help, you'd be better served to find a more purely-windows-specific forum... 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/