#42 Problems with menu on UIQ

[Rick Andrews]

The OPL runtime menu handling doesn't fit very well with the UIQ
style guide of having the menu on screen at all times.

Ideally, the menu bar should appear at start up, and remain
available for use at all times.

The short-term workround here is to press the jog-dial button in to
(re)launch the OPL menu.

[Pawel Durys]

Logged In: YES
user_id=954979

I have an idea how to workaround this.

If you catch the ThreadID of loaded app with menu, you can
SendKeys to this app and show menu at startup.

This is based on the
\oplr\opltest\Automatic\xPMainI\spMenu.tpl code.

[Rick Andrews]

Logged In: YES
user_id=719915

Cut'n'pasted from the OPL Wiki:

"...the Menu Bar should be displayed at ALL times... But in the
OPL implementation it does not appear until it is called using
the Confirm button. So how can I make it appear all the time
from program start ? (and referring back to a previous
message, make it usable all the time without having to press
the Continue button)

[solution] App Frame OPX needs a new function to fill an OPL
window with the menu bar graphic using the menu card titles.
This is called early on, during app initialisation. For example:

AFInitUIQMenu%:(1, File, Edit, Tools)
where 1 is the OPL window id, in this case, the default
window.)
The jog-dial push button functionality can be changed, from
launching the menu in the Beta, to its own independent
value Ewan suggests KKeyMenu32& or (even better)
KKeySidebarMenu32& to retain compatibility with other OPL
runtimes. ] Al suggest a unique code so that the
programmer can control it.