Newsgroups: comp.windows.ms.programmer
Path: utzoo!utgpu!watserv1!sunee!gpsteffl
From: gpsteffl@sunee.waterloo.edu (Glenn Patrick Steffler)
Subject: Re: What's wrong with SetDlgItemText()?
Message-ID: <1991Feb25.233015.1164@sunee.waterloo.edu>
Organization: Gerbils On Speed Inc.
References: <1991Feb23.223755.817@javelin.es.com>
Date: Mon, 25 Feb 1991 23:30:15 GMT
Lines: 29

In article <1991Feb23.223755.817@javelin.es.com> lwallace@javelin.es.com (Lynn Wallace) writes:
>I use this function frequently in my WM_INITDIALOG portion but in setting the
>text of one edit control, it terminates my application.  So I shelled out $70
>for a secondary monitor and ran CVW on it, and IT reported "Application
>terminated normally" after I execute the function call!  Does anyone know under
>what conditions SetDlgItemText() may do this?

Pretty heavy duty expense to test a funtion call.. :-)

SetDlgItemText() is simply an alias for SetWindowText().  Make sure the
dialog box you are using has been exported, etc.  Codeview sometimes
has trouble when I don't trace thru at least one line of code before 
running until a break point.  Never has any other problems though.

>Windows 3.0 SDK:  I am not impressed.

I am!  ( :-) - for those in the know)

>-- 
>Lynn Wallace			   |I am not an official representative of
>Evans and Sutherland Computer Corp.| <- E&S.  Or for that matter, unofficial.
>Salt Lake City, UT 84108	   |Internet: lwallace@javelin.sim.es.com
>			War not make one great! -- Yoda

-- 
Co-Op Scum                            "Bo doesn't know software" - George Brett

"The galaxial hearth steams the sea as the sky blood red embrasses darkness"
-John Constantine (HellBlazer)                          Glenn Steffler