Replacement for the DBI ctText ActiveX control (styled label)¶

Project: User Interface

Problem¶

ctText (ctText.ocx 3.0) is not a text editor but a small styled label. Applications set Caption (short state tokens, and glyphs from the Webdings font), ForeColor, ForeColorOver and BorderColor, and handle Click. One pattern overlays a ctText on an image thumbnail as a delete-mark toggle.

Work¶

1. Convert ctText into a native TEXT widget (or an IMAGE widget where it shows a glyph), carrying the colours, the hover colour and a Click event.
2. Provide image substitutes for the Webdings glyphs, which the browser does not have.
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.