Skip to main content

[archive] Native Controls

  • October 19, 2010
  • 1 reply
  • 0 views
D

[Migrated content. Thread originally posted on 18 October 2010]

I was curious if any one is currently using or has tried using the WIN32_NATIVECTLS (native controls) feature to get the more updated interface. We had issues in the past with transparency of the labels of Radio Buttons and Check boxes not being transparent on tabs, but it appears that this has been fixes successfully in the 9.0 version of extend. The latest problem we are having is with the ability to tell if a check box or radio button has the focus. Since windows vista, windows has turned off by default the Quick Access Keys, which means that in order to see the underlined quick key short cuts, you need to press the ALT key to see the quick keys. Apparently the feature that puts the dotted frame around the check boxes and radio buttons is somehow tied to this in the runtime. So, for uses on Vista or Windows 7, if you use the native controls feature, the user cannot necessarily tell which field has focus unless the user changes the windows default settings. I am wondering if anyone else has experienced the same problem that we are having and if so, are you or your end users having an issue with this?
Thanks,
Scott

    1 reply

    D

    [Migrated content. Thread originally posted on 18 October 2010]

    I was curious if any one is currently using or has tried using the WIN32_NATIVECTLS (native controls) feature to get the more updated interface. We had issues in the past with transparency of the labels of Radio Buttons and Check boxes not being transparent on tabs, but it appears that this has been fixes successfully in the 9.0 version of extend. The latest problem we are having is with the ability to tell if a check box or radio button has the focus. Since windows vista, windows has turned off by default the Quick Access Keys, which means that in order to see the underlined quick key short cuts, you need to press the ALT key to see the quick keys. Apparently the feature that puts the dotted frame around the check boxes and radio buttons is somehow tied to this in the runtime. So, for uses on Vista or Windows 7, if you use the native controls feature, the user cannot necessarily tell which field has focus unless the user changes the windows default settings. I am wondering if anyone else has experienced the same problem that we are having and if so, are you or your end users having an issue with this?
    Thanks,
    Scott
    Yes we have noticed this as well, it's very fustrating. One thing we have done is to change the COLOR of the current control to some user defined color as the user moves thru fields, and switch the last control back to white, all in the Form's Bef-Procedure. This isn't fool proof as some controls (like drop down combo-lists don't completely color, and some controls like radiosets need to be changed back to grey not white). But overall it works pretty well to know where you are on the Form.

    We thought of using an API call to modify the quick access keys windows preference, but thought it might not be such a good idea...

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement