home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.programmer
- Path: sparky!uunet!psinntp!panix!os2man
- From: os2man@panix.com (Larry Salomon Jr.)
- Subject: Re: Button Press..HELP!!!!
- Message-ID: <1992Jul22.020524.17316@panix.com>
- Date: Wed, 22 Jul 1992 02:05:24 GMT
- References: <seOXNpS00Vp9AAAUxL@andrew.cmu.edu> <1992Jul20.182305.21192@cs.umn.edu> <harris.711681425@garfield.catt.ncsu.edu>
- Organization: PANIX Public Access Unix, NYC
- Lines: 23
-
- In <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.)
-
- I just jumped into this conversation, so pardon me if this has been answered:
- Pushbuttons send a WM_COMMAND message with SHORT1FROMMP(mpParm1) equal to
- the id of the button that was pressed.
- --
- Cheers,
- Q
- -----------------------------------------------------------------------
- "If you still choose not to decide, | "My other account is in the
-