Profound Logic Forums

Rick,

The easiest way to tell if the fields are like this is to open Genie and turn on the Design Mode. Then click one of the fields, this should show if all of the Cmd n- text is contained in one field, or if each is it's own separate field.

Looking at the examples you gave here of Cmd n- xxxxx, or Cmd nn--xxxx, this should be something that could be detected with some JavaScript and regular expression. It's definitely a possibility, and something I could look at. If you take a look at my 2nd post here it shows how to obtain a screendump from Genie. Are you using a custom skin you've created? Or one of the defaults?

Using a custom skin per Genie recommendations not to mess with supplied.

Rick,

Thanks for that. So in addition to the screendump we'd need a copy of your Genie skin folder so we could see your screens how you do. This is easy to obtain, if you have access to your IFS you should be able to find your Genie skin folder under the following location /www/your instance/htdocs/profoundui/userdata/genie skins (by default). If you zip this up and send it with the screendump to trial@profoundlogic.com. I should be able to take a look at this.

Was there a resolution to this? I am having the same issue. Where can I find the code that detects the function keys?

There are a couple of configuration options that have been added in the last few releases that might help.

Function Key Pattern (version 5.1.2)
http://www.profoundlogic.com/docs/displ ... ey+Pattern

Function Key Pattern 2 (version 5.6, I think)
http://www.profoundlogic.com/docs/displ ... y+Pattern2

See if one of those configuration options resolve your problem.

Glenn

Glenn,
Most of our function keys have a space between F# and the =, so neither of those options catch them. Would it be difficult to make a third one that will allow for the space?

Patti

I just did a quick test using regex101.com (selected the JavaScript flavor) and the following regex matched to "F3 = Exit". Please try the following configuration setting to see if it works. Notice the addition of the "\s*", this will look for from 0 to more spaces after the command key text but before the separator.

pui["function key pattern"] = "^(F|CA|CF|CK|CMD)([0-9]{1,2})\s*([=:-])(.*)$";

Glenn

I modified genie.js adding the \s*, but no luck.

Here is a copy of the line of code: pui["function key pattern"]="^(F|CA|CF|CK|CMD)([0-9]{1,2})\s*([=:-])(.*)$";

Patti

You shouldn't modify the genie.js file. See the instructions below for where to put configurations settings.
http://www.profoundlogic.com/docs/displ ... on+Options

Glenn

Okay....I added the line to the settings.js in profoundui\htdocs\profoundui\userdata\custom\js but it still did not work. Any other ideas?