Replacement for the DBI ctFold ActiveX control (tab strip)¶

Project: User Interface

Problem¶

ctFold (ctFold.ocx 3.0) is a tab strip. Applications use SelectedTab heavily, change Caption and Amount at run time in a few places, and set tab images through PicSequence. The TabChange event shows and hides a frame per tab. One screen vetoes a tab switch on unsaved data through CheckChange and CancelChange. The tab captions are set at design time in the .wrx.

FWD's TABSET has no COM events, no tab images and no cancelable change.

Work¶

1. Map ctFold onto TABSET and add the TabChange event, a cancelable CheckChange, tab images and run-time caption and count changes.
2. Take the captions from the .wrx.
3. Register the control's CLSID in the OCX registry (ocx-registry.xml), mapping it to the target widget, as #11919 did for ctToolBar.
4. Decode the design-time state the control keeps in the .wrx storage at conversion time, so that it exists after conversion.
5. 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.
6. 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.
7. 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.