[Oorexx-rfes] [ oorexx-Feature Requests-1772723 ] ooDialog: consistent handling of WS_GROUP, WS_TABSTOP, etc.

[SourceForge.net <no...@so...>]

Feature Requests item #1772723, was opened at 2007-08-12 12:11
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1772723&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: External Functions
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mark Miesfeld (miesfeld)
Assigned to: Mark Miesfeld (miesfeld)
Summary: ooDialog: consistent handling of WS_GROUP, WS_TABSTOP, etc.

Initial Comment:
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.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1772723&group_id=119701