Feature #12055
Microsoft common controls: TabStrip, Toolbar, ImageList and ProgressBar
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:
History
#1 Updated by Greg Shah 14 days ago
Microsoft common controls: TabStrip, Toolbar, ImageList and ProgressBar¶
Project: User Interface
Problem¶
Four Microsoft common controls (MSCOMCTL.OCX) map onto FWD widgets:
| Control | Used for | Target | Missing |
|---|---|---|---|
| TabStrip | Tabs:Add, SelectedItem, key and tag per tab, Click |
TABSET | a click event on the tab, key and tag per tab |
| Toolbar | Buttons:Add, ButtonMenus:Add, ButtonClick, ButtonMenuClick, ImageList |
CT-TOOLBAR (#11919) | the Microsoft member names and the button menus |
| ImageList | an icon source for ListView, TreeView and Toolbar, with images embedded in the .wrx; ListImages:Add, ListImages:Clear |
IMAGELIST | the .wrx image extraction |
| ProgressBar | VALUE |
PROGRESS-BAR | nothing |
Work¶
- Register each control in the OCX registry with its target, and add the alias and event tables.
- Add the missing pieces listed above, sharing the TABSET work with the ctFold replacement.
- Register the control's CLSID in the OCX registry (
ocx-registry.xml), mapping it to the target widget, as #11919 did for ctToolBar. - Decode the design-time state the control keeps in the
.wrxstorage at conversion time, so that it exists after conversion. - Implement the members and events listed above on the target, with the vendor's semantics: argument types, return values, defaults, and the order in which events fire. Members of the type library that are not used become no-ops with a conversion warning, as the OCX pipeline already does.
- Follow the OCX emulation playbook attached to #11919: an OpenEdge test program with goldens for each member and event, recorded input sequences for the interactive parts, and Lyra automation.
- Update the gap marking and the OCX registry documentation.
Testcases¶
Each member and event above, exercised on Windows OpenEdge with the real control to produce goldens, then run against the FWD replacement on the web and Swing clients. The vendor help files are the reference where behaviour cannot be observed directly.