#220 ooDialog: consistent handling of WS_GROUP, WS_TABSTOP, etc.

v3.2.0
closed
5
2012-08-14
2007-08-12
No

In the Windows UI there are a group of 5 styles that every dialog control can have, or not have.

They are WS_VISIBLE, WS_DISABLED, WS_BORDER, WS_GROUP, and WS_TABSTOP. Under the covers in the C functions, ooDialog adds or takes away these styles when the different controls are created.

There are 2 problems here:

1.) The documentation does not explain that these styles are available for all controls and does not document how to add or take them away for all controls.

2.) The C functions are not 100% consistent in allowing all controls to have or not have the 5 styles. For instance, for an edit control (addEntryLine) there is no way for the user to remove the WS_TABSTOP style.

I intend (unless Chip strenously objects <grin>) to change this by:

1.) Fixing the C code so that the user can define every control either with or without each of these style.

2.) Updating the documentation to clarify this issue for the user.

Discussion

  • Mark Miesfeld

    Mark Miesfeld - 2007-08-24

    Logged In: YES
    user_id=191588
    Originator: YES

    Committed revision 710.

    This commit fixes the code so that in subclasses of the UserDialog, it is possible to add or remove the following Windows window styles for any dialog control: WS_VISIBLE, WS_DISABLED, WS_BORDER, WS_GROUP, and WS_TABSTOP. This effects dialog created from a resource script and dialogs created using the Add... methods. Dialogs created from a compiled binary file (a .dll file) have always had this ability because they were not dependent on ooDialog. The dialog controls were created however the user defined them in the biary resource.

    So that was the first part of this RFE. The second part is to document this correctly. Still working on that.

     
  • Mark Miesfeld

    Mark Miesfeld - 2007-09-19

    Logged In: YES
    user_id=191588
    Originator: YES

    Committed revision 772.

    Fix the addBitmapButton method so that the user can specify whether the button will or will not be a tabstop.

     
  • Mark Miesfeld

    Mark Miesfeld - 2007-10-06

    Logged In: YES
    user_id=191588
    Originator: YES

    The code is fixed so that the user can define a control either with or without any of the 5 window styles.

    I have added a section with a generic explanation of the styles to the ooDialog reference. This section also explains, basically, how to add or remove the styles from any type of dialog control.

     


Anonymous

Cancel  Add attachments