>>>A question that remains is that the attributes of menu bars are not (normally) defined as object properties. Fortunately, using an OOP based menu will help to minimize the effort of handling this specific case.
>>
>>The menu was relatively easy to fix for us. Since this is a very old codebase, it used the menu generator to build the menu. So I changed the menubuilder (genmenu) so that it would macrosubstitute all FONT references in the MPR file:
>>
>>In the genmenu code:
>>

>>   \\ PROMPT "<<m.prompt>>" FONT m.gcMenuFont, &gcMenuFontsize
>>

>>That results in the following MPR file:
>>

>>DEFINE BAR 25 OF analysen PROMPT "\<Kosten" FONT m.gcMenuFont, &gcMenuFontsize ;
>>	SKIP FOR ! m.erwFlag 
>>

>>
>>That is not the most elegant way, but efficient.
>
>Wasn't the trick for font and style in PROMPTS to alter the SKIP for field in the designer after the skip code? Just put the stuff into it?
>So that the designers SKIP field looks like: ! m.erwFlag FONT m.gcMenuFont, &gcMenuFontsize in your case?

That could be working as well, but then I had to change all menu bars. So it was easier to handle this in the generator.