Re: Check a radio button

I am not rigid, and there are times where I have used GetDlgItem, but in
general:
If it's a control that was already on the dialog then it should have a
variable attached to it to begin with.

Are we talking about a DLL or an ActiveX control?

I don't think that adding a variable would have any consequences to a
calling program.

AliR.

"Ashot Geodakov" <a_geodakov@xxxxxxxxxxxxxxxxxx> wrote in message
news:e9wIdh7oHHA.4696@xxxxxxxxxxxxxxxxxxxxxxx
Comments:

"AliR (VC++ MVP)" <AliR@xxxxxxxxxxxxx> wrote in message
news:rTE7i.23716$YL5.4248@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I agree with Joe no this, why would you have a control on a dialog if you
don't have a variable attached to it?

Someone from a parallel group comes to you and asks you to change
something in your dialog, but makes a special request not to add any more
variables to the dialog's header file. What if all they have from you is a
header, and they include it all over? Then two separate components ship,
yours with an extra variable, and theirs without - consequences?

In a "normal" organization things like that are less likely possible. In
an organization like MS, with all their bureacracy, you may want to think
10 times before changing your interfaces.

How would you manipulate the control?

Through (Control*)GetDlgItem( ... )

So that fact that he said that creating a variable for the control is
fundamental, is 100% true. (Unless all your controls are static controls)

Every situation is different.


AliR.

"Ashot Geodakov" <a_geodakov@xxxxxxxxxxxxxxxxxx> wrote in message
news:eso0jJ7oHHA.4032@xxxxxxxxxxxxxxxxxxxxxxx
Are you always like this?

Adding an extra member to a class increases the object's size. I don't
know why it can be a problem, but who knows what kind of code out there
depends on a fixed object's size?






.

Loading