home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.programmer
- Path: sparky!uunet!darwin.sura.net!mips!mips!decwrl!csus.edu!netcomsv!mork!msmith
- From: msmith@netcom.com (Martin P. Smith)
- Subject: Re: Button Press..HELP!!!!
- Message-ID: <hjdmfk+.msmith@netcom.com>
- Date: Tue, 21 Jul 92 07:34:52 GMT
- Organization: Netcom - Online Communication Services (408 241-9760 guest)
- References: <seOXNpS00Vp9AAAUxL@andrew.cmu.edu> <1992Jul20.182305.21192@cs.umn.edu> <harris.711681425@garfield.catt.ncsu.edu>
- Lines: 26
-
- In article <harris.711681425@garfield.catt.ncsu.edu> harris@garfield.catt.ncsu.edu (Michael Harris) writes:
- >joiner@cs.umn.edu (Jay Joiner) writes:
- >
- >> Of course, if you have two or more buttons, then you have
- >>to differentiate somehow. One theory I had was to save the window handle
- >>for each button when you create them with WinCreateWindow, and then
- >>query to find out which caused the WM_COMMAND message to be sent using
- >>the parameters. I don't have any 2.0 docs, so I don't know the correct way
- >>to handle these cases.
- >
- >The best way is to give each of your buttons a unique window id. One of
- >the message parameters contains the window id of the button pushed. (I don't
- >have my docs handy so I am not sure which one it is at the moment.)
- >______________________________________________________________________________
- > Michael Harris - harris@catt.ncsu.edu or harris@carvm3.vnet.ibm.com
- > System Administrator, Computer & Technologies Theme Program, NC State Univ.
- >(My opinions are my own and do not represent those of NCSU or IBM Corporation)
-
-
- Are the structures _COMMANDMSG and COMMANDMSG different beasts??? _COMMANDMSG
- exists from lines 931 thru 938 in pmwin.h .
-
-
- Martin Smith
- msmith@netcom.com
-
-