Shortcut keys

[adSProfound4711]

We seem to have a severe problem with "button" (widget type image) shortcuts.
We use them to switch between modes like DELETE, EDIT, ADD and have defined shortcut keys for them.

Depending on the user's authority and/or the current state of the program we sometimes disable the buttons.

Unfortunately the shortcut keys are still enabled.
Apparently this is not the case with "old" Profound screens compiled 1 or 2 years ago.

Is the intended?

Best wishes,

Rainer aus dem Spring

[Scott Klement]

Hello Rainer,

This is not a change. The shortcut key on buttons has always activated them, even when they are hidden. (I tested all the way back to 2012.)

This was done purposefully, because sometimes customers want their users to be able to use a function key when there is no button on the screen. This way, it can appear to the user as if there's no button on the screen.

Good Luck

[adSProfound4711]

Hello Rainer,

This is not a change. The shortcut key on buttons has always activated them, even when they are hidden. (I tested all the way back to 2012.)

Erm, I am talking about images used as buttons and I am talking about disabled, not hidden.
Some of the programmers of our customer have created customized widgets which we drag into new Profound screens.
Something must have happened some time ago.

Perhaps you can have a look at the two buttons in two files - see attachment.
One of them disables the shortcut F4 if disabled, the other one does not.
For us this is a disaster. We disable the Delete button in certain situations or for users not allowed to delete records.
Unfortunately they can still press F4 although the "button" is disabled,

Best wishes,

Rainer

[Scott Klement]

Apologies for the misunderstanding of images vs. buttons and visibility vs. disabled properties. I understand now.

I am unable to reproduce the problem you have described. For me, if the button is disabled, the shortcut key does not work. When it is enabled, it does work.

I have compared the two buttons you have provided. They are nearly identical, but there is a small difference.

In STARB002D, the button's visibility property looks like this:

Code: Select all

   "visibility":{
      "fieldName":"DBTNDE0002",
      "customTrue":"",
      "customFalse":"",
      "dataType":"indicator",
      "formatting":"Indicator",
      "indFormat":"visible / hidden",
      "longName":"dBtnDeleteVisible"
   },

In STVPR021D, the visibility is different:

Code: Select all

   "visibility":{
      "fieldName":"DBTNDE0002",
      "customTrue":"",
      "customFalse":"",
      "dataType":"indicator",
      "formatting":"Indicator",
      "indFormat":"1 / 0",
      "longName":"dBtnDeleteVisible"
   },

For this reason, the 'visibility' property on STVPR021D does not work for me. However, this difference does not affect whether the shortcut key property works. In all versions that I have tested, the disabled property continues to block the shortcut key from working. It never allows the shortcut key when disabled.

You might consider reporting this to Profound Logic Support, perhaps they will think of some reason why this might not work.