implement conversion support for CONTEXT-HELP, CONTEXT-HELP-FILE and CONTEXT-HELP-ID as runtime stubs¶

Project: User Interface

Problem¶

CONTEXT-HELP and CONTEXT-HELP-FILE are frame options for Windows context-sensitive help: CONTEXT-HELP puts a question mark button in a dialog's title bar, CONTEXT-HELP-FILE names the help file, and the CONTEXT-HELP-ID widget option selects the topic. For example:

DEFINE FRAME Dialog-Frame
   ...
   WITH VIEW-AS DIALOG-BOX CONTEXT-HELP CONTEXT-HELP-FILE "app.hlp".

DEFINE BUTTON bn_ok LABEL "OK" CONTEXT-HELP-ID 0.

Neither frame option converts and neither has a runtime; the gap marking records both as None / None. Context-sensitive help depends on the Windows help engine, which a converted system, and especially a web client, does not have. But a program that uses these options has to convert and run.

Work¶

1. Convert the CONTEXT-HELP and CONTEXT-HELP-FILE frame options and the CONTEXT-HELP-ID widget option, in frame definitions and frame phrases, including the forms the AppBuilder generates.
2. Provide the attributes at runtime so that they can be read and assigned: CONTEXT-HELP, CONTEXT-HELP-FILE and CONTEXT-HELP-ID store and return their values.
3. Do not show a help button and do not call any external help engine.
4. Check that SYSTEM-HELP and the HELP key (applhelp.p on the PROPATH) convert and run in the same programs.
5. Update the gap marking to Full conversion and Stubs at runtime.

Testcases¶

• A dialog with CONTEXT-HELP only, one with CONTEXT-HELP-FILE naming a file that does not exist, and buttons with CONTEXT-HELP-ID: each converts, runs and returns the stored values.