Keyboard Maps screen displayed

[pravik]

Hi All,

We have encountered a scenario were, when we click on some tabs we get "Keyboard Maps Screen" as attached. But when we tried to replicate the same, we were not able to do so. Hence wanted to know under which scenario does this screen appear and how do we avoid this.

Thanks & Regards,
Priya

[MarkD]

If you run aXes session outside RAMP the keyboard comes into view if you click on either of these controls:

Capture1.PNG (21.85 KiB) Viewed 13751 times

when clicked the keyboard slides in:

Capture2.PNG (37.3 KiB) Viewed 13751 times

Have you every seen these controls appear on a RAMP screen, especially the very narrow bar on the lefts screen edge?

[MarkD]

Also, in you screen shot - do you know what this area is?

image1.PNG (67.19 KiB) Viewed 13746 times

[pravik]

Hi Mark,

Apologies for late reply.

In Axes we are aware of this, but we are worried as of how its getting displayed in URL.

In the screen shot the area which u have highlighted, there to the left top corner the actual screen which is supposed to be loaded is shown. But we aren't sure of what is that area. Can you please tell on what scenarios does this (Keyboard map screen) appear and how do we avoid it.

Thanks & Regards,
Priya

[MarkD]

The first time a screen arrives RAMP executes GLOBAL_oAXESInterface.UI.sideBar("hide") to hide the controls that allow access to the virtual keyboard.


Does any of your RAMP scripting refer to a function named XXXXXXXXX.UI.sideBar("show") or something like that?
In the very, very unlikely event that it does ....... that would bear investigation.



Do you know if any function key or other accelerator can cause the sidebar menu to appear in a normal aXes session?
I don't know the answer to that one, but maybe such a key exists and is being used by accident.



Have you every seen the any of sidebar controls previously pictured previously appear on a RAMP screen, especially the very narrow bar on the screens top, bottom, left or right edge?


Can you reproduce the scenario? If you can that would be invaluable for LANSA support.

[pravik]

Hi Mark,

We would check regarding "UI.sideBar" in RAMP and get back with feed back.

Meanwhile in order to replicate such scenario, it would occur only when we have high CPU percentage were URL doesn't load.

Thanks & Regards,
Priya

[MarkD]

High CPU on the IBM i server or on th e PC running the web browser?

[pravik]

It's high CPU percentage in IBM i server.

As of now we were able to find only this scenario, we are not pretty very sure if we have any-other way to replicate the same.

[pravik]

Hi Mark,

We couldn't find GLOBAL_oAXESInterface.UI.sideBar in ramp scripts.

Looks like this would be part of May2018 EPC, currently we have V14 SP1.

Kindly correct me if my understanding is wrong. Please let us know how to avoid this from occurring.

Thanks 7 Regards,
Priya

[MarkD]

Then it look like a defect that you will need to report to LANSA support.

If you can get a cache cleared Fiddler trace of this happening then that would be huge boost to the chances of a rapid resolution.

Also, when it happens try using these accelerator keys to see if you can make the keyboard disappear and show you what the small 5250 screen is.

Capture.PNG (33.55 KiB) Viewed 13656 times