on 06-17-2015 9:21 AM
Hi All
It was hard to describe what I am trying to say but its best explained in screenshots.
What I have found is that if a user is in one of my flavors, in this case PA40 it works fine if you just click in any of the correct fields, in this case I am in the Position field:
If I then click anywhere else on the screen the Green Back Arrow gets highlighted:
If I then press enter obviously this triggers the back function.
Upon looking further, I have hidden the menu button: which does get highlighted if I clicked anywhere on the screen.
My question is how do I stop a button being highlighted when a user uses the mouse to click any area of the screen?
I hope this has made sense!!
Ian
I
Hi Ian,
This is because toolbar has tabindex 0 and menu button has index 0 in it. Since you have hidden menu button and tcode box and execute button, focus goes to next button which is back button.
You can change this behavior by changing the tab index of toolbar (tbar[0] and tbar[1]) to 1 and tab index of Pers no input box to 0.
Hope that helps.
Thanks
Chinthan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Angus,
You can change by going into edit flavor mode and selecting toolbar and opening properties editor (show/hide properties button on top right corner of editor) and then changing the tab index property value. Similarly select your control and update tab index from properties editor.
Thanks
Chinthan
I now have an update on this. I am now in the process of adding a script button to every screen used in my Personas build. I place this on the menu bar as the first button, then make the border, background and foreground colours Transparent.
What then happens is when a user clicks anywhere within any screen/transaction, if they are not clicking a field or button, it simply highlights the blank script button. If a user then presses enter, nothing happens save for the script button to be visible until they click elsewhere.
Not an ideal solution, but certainly solves the issue of a user clicking in a blank area, then pressing enter and performing an action that they did not choose to do.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.