I find it very difficult that you named your controls same as the standard VB controls.
I know it would be a big change to alter them, but maybe it's better to do it now than to do it later...
At least I am struggeling a lot with it because I never know which control I'm dealing with.
Thank you.
Name of controls
Re: Name of controls
This would break compatibility, so no chance.
Crunching for Fab36_Folding-Division at Folding@Home. Join Fab36/Fab30! - Folding@Home and BOINC
Boycott DRM! Boycott HDCP!
Boycott DRM! Boycott HDCP!
Re: Name of controls
There are good and free OCX renamers.
But... why did you give them the same names in the first place?
But... why did you give them the same names in the first place?
Re: Name of controls
Because I don't see it as a problem such big that it would justify worse control names.
In which places can you mix up my controls with the standard ones?
1) In the property grid. Since my controls have different properties, it's not that difficult to tell which control is standard and which one isn't.
2) In the object browser. There's a combobox with which you can filter the displayed objects by the library containing them.
3) In the source code when defining new object variables (Dim btn As OptionButton). You can use BtnCtlsLibUCtl.OptionButton instead.
In which places can you mix up my controls with the standard ones?
1) In the property grid. Since my controls have different properties, it's not that difficult to tell which control is standard and which one isn't.
2) In the object browser. There's a combobox with which you can filter the displayed objects by the library containing them.
3) In the source code when defining new object variables (Dim btn As OptionButton). You can use BtnCtlsLibUCtl.OptionButton instead.
Crunching for Fab36_Folding-Division at Folding@Home. Join Fab36/Fab30! - Folding@Home and BOINC
Boycott DRM! Boycott HDCP!
Boycott DRM! Boycott HDCP!