OvationPro sets NumLock on xM?

I’ve installed Ovation Pro 2.77s on my BB-xM. Opening a document window, OvnPro sets NumLock on. It’s not possible to reset NumLock whilst the window is still open.

I have one of the keyboards that requires FX 202 & 118 in BootRun.

Is this a known issue?

[Later] By way of amusement I altered Ian Hamilton’s NumOn to be NumOff and ran OvnPro. It killed the NumLock and when I quit NumOff the NumLock stayed off. Until I opened another document, that is.

Probably not a long term solution :-)

[Still later] REMming out RMEnsure UniversalKey in PlingOvnPro.PlingRun allows NumLock to be switched off once in a document though opening one still sets it.

I see a similar problem was raised on DP’s mailing list in 2007. There, whilst the UniversalKey module was raised as suspect, it was concluded that HID was to blame. That’s not what’s happening here – definitely the keyboard module. The module seems capable of patching for different systems but I don’t see how the options are available to OPro unless OP does system detection.

For completeness, David P gave me this solution a while back. It worked.

>Num Lock
>
>void keyboardmode(int mode);

>#define KEYNUMLOCKKEY 0×1 – Num lock
>#define KEYBREAKKEY 0×2 – Break generates codes
>#define KEYAUTORATE 0×4 – !Auto repeat
>#define KEYACTIONKEY 0×8 – Action key != Control key
>#define KEYSCROLLLOCKKEY 0×10 – Scroll lock

>Default – (KEYNUMLOCKKEY|KEYSCROLLLOCKKEY)

So you stick a

keyboardmode(0×10);

In your PlingOvnPro.AutoRun.!Custom file, and it stops messing about with Numlock.