Page 1 of 1
VLF-One Keyboard Mapping
Posted: Fri Apr 10, 2020 10:20 pm
by rgjohnson
Where is the keyboard mapping done for axes screens used in VLF-One?
It seems the default mapping for the CTRL key is FIELD EXIT. Users are complaining about not being able to use CTRL-C and CTRL-V to copy/paste data from input fields. I have tried updating the defaultkeymap.xml file and my updated file is the one being loaded into the browser, but the mapping rules I have added are having no impact. When you select an input field and press CTRL, it clears the input field immediately and does not allow use of CTRL-C.
Re: VLF-One Keyboard Mapping
Posted: Sat Apr 11, 2020 4:13 am
by rgjohnson
I have confirmed the defaultkeymap.xml file is the correct file, but the mappings are not working correctly it seems to me.
By default the Ctrl key is mapped to FIELD EXIT. If you then map any combination using the Ctrl key (Ctrl+C, Ctrl+X, Ctrl+NewLine, etc...) those mappings work, but the Ctrl key by itself (so FIELD EXIT) is processed before the combination is processed.
If you click on a field and use Ctrl+C it processes FIELD EXIT thereby blanking out the field, and then it processes the Copy with blank data.
Ctrl+NewLine processes FIELD EXIT first, and the processes NewLine after it blanks out the field you were originally on.
Is there any way around to resolve this here or is this a support issue?
Re: VLF-One Keyboard Mapping
Posted: Mon Apr 13, 2020 11:53 am
by MarkD
Do you still need a field exit key in the aXes/RAMP 5250 parts of the application?
Also, I would expect the Ctrl key behaviour to be different between fields on an aXes/RAMP 5250 screen and fields in a "normal" VL-Web panel area.
Is that what happens?
Re: VLF-One Keyboard Mapping
Posted: Wed Apr 15, 2020 9:31 pm
by rgjohnson
Hi Mark, definitely need a Field Exit key on the 5250 portion. Users doing data entry and transaction maintenance use it all the time. Mapping the Ctrl key to Field Exit as the default makes sense as that is what most people do with 5250 emulators anyway.
The issue I am having is that mapping the Ctrl key to Field Exit prevents you from using any combination that uses Ctrl since the Field Exit command is always executed first. When I test this on other 5250 emulators it seems the Ctrl key when pressed alone does not execute any command until you let go (button-up). If you use the Ctrl key in combination (Ctrl+C, Ctrl+X, etc...) it seems to process all other commands onclick of the last key in the sequence.
I am not sure about your question of different keyboard behavior between 5250 screens and VL panels. I tried testing that just now but could not get the Ctrl key to act differently between the two situations.