Re: Help Brainstorming
Thanks. I kind of have it working now as a separate combo box and button.
:-) It works okay. I was thinking if I needed it in a bunch more places, or
needed lots more functionality, some sort of control would probably be
needed.
I just started thinking how easy this has been in some languages, and how
VC++ doesn't really have a very simple way. But, you're right and perhaps
it's not worth messing with.
--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com
"David Ching" <dc@remove-this.dcsoft.com> wrote in message
news:D0CBED2E-5022-47FC-924D-10AF1A9AFAD4@microsoft.com...
"Jonathan Wood" <jwood@softcircuits.com> wrote in message
news:OXi3XX9JJHA.2348@TK2MSFTNGP02.phx.gbl...
Can anyone think of a simpler way?
I think you've pretty much got it, but I would derive your control from
CStatic. Then you could put a static control in your dialog and assign a
DDX control variable of your control class to it, rather than going the
user control way. It's easier, I think.
When it's created (or subclassed, if it's attached to a dialog control),
create child controls of CComboBox(Ex) and CButton. The hard part is
sinking events like the button being clicked, or the combobox dropping
down, since you want to handle these events in your dialog (or parent
window), but Windows will route these events to the parent window which is
your CStatic derived control and not to the dialog. Then you're stuck
forwarding the messages to the dialog.
All things considered, I would probably just stick with a separate
combobox and button! ;)
-- David