-basekey, -ininame startup parameters ignored in a .pf file.

In the AppBuilder perspective of PDS for OpenEdge, when viewing a .w file in the visual designer, getting error message, "** Font <font-number> not in Font Set. (4499)".
 

Window->Preferences->Progress OpenEdge->Startup includes -pf and a pf file name.
The PF file includes -basekey -ininame and the name of an .ini file.
The .ini file contains a reference line to the font number that is flagged as not in the font set.

This is expected behavior.
According to the Startup Command and Parameter Reference, Startup Parameter Descriptions : Registry Base Key (-basekey):
Note: You can use the -basekey startup parameter only at the command line. It is ignored when used in a parameter (.pf) file.
The same restriction is documented for the -ininame startup parameter.

The AVM follows the set of rules detailed at Progress Documentation: Searching progress.ini and the Registry at startup (https://docs.progress.com/bundle/openedge-abl-manage-applications-117/page/Searching-progress.ini-and-the-Registry-at-startup.html) .
 

Include the -basekey "INI" -ininame <.ini file name> in the startup parameter line in Window->Preferences->Progress OpenEdge->Startup or include it as a command line startup parameter.

References to other documentation:

https://documentation.progress.com/output/OpenEdge117/openedge117/#page/dpspr%2Finitialization-file-(-ininame).html

https://documentation.progress.com/output/OpenEdge117/openedge117/#page/dpspr%2Fregistry-base-key-(-basekey).html