F-Keys on 5250 Windows

[khoreis]

F-Keys do not appear on 5250 Windows. They disappear.

[Scott Klement]

The F-keys seem to appear for me when I try them. Please try the following:

1) Try running one of the default Profound Logic skins, such as Gradient or Classic. Do the function keys appear in that skin? If not, the problem is in Genie. But, if they do, then the problem is in the skin itself.

2) If the problems did occur in the stock Profound Logic skin, please hit Ctrl-F9 on one of the problem screens. The browser will ask you to download a file named json.txt -- please post that here or e-mail it to us.

3) If the problem idd not occur in the stock Profound Logic skin, then please find your skin (the one with the problem) in the /www/PROFOUNDUI/htdocs/profoundui/userdata/genie skins directory of your IFS. There will be a directory named after the skin you're using. Please zip up that entire directory and post it here or e-mail it to us.

You can e-mail us at support@profoundlogic.com.

[khoreis]

The problem is in a skin created for us by David for Proof of Concept. FYI - We have not gone through training yet, it's really busy here right now and I'm trying to get this started when I have bits of time. Here is the JSON.txt file

[Scott Klement]

One of our stock skins (Hybrid) will move all of the function keys into a little menu on the left to make things more web-like. Could that be what you're seeing? Here's what it looks like:

linkmenu.png (44.16 KiB) Viewed 3769 times

If that's not it, then you'll need to send me the skin (as I mentioned in the earlier message.) This screen seems to work fine in the skins I tried it with.

[khoreis]

Those F-Keys shown are from the screen behind it. Would you software share them? I only have 2 F-Keys on the Window, F3=Exit and F4=Prompt.

[khoreis]

Here is the skin

[Scott Klement]

Kevin,

I loaded your Genie skin, and it seems to be doing what I mentioned earlier. It's moving the F-keys to the menu on the left. See the following screenshot:

linkmenu2.png (68.99 KiB) Viewed 3759 times

You said these are from the underlying screen -- but, the underlying screen didn't have an 'F04' on it, so this must be coming from the window. Also notice that it has two F12's on it, that's because one came from the underlying screen (the Frt Mthd one) and the other came from the window.

The code that does this is in the 'custom.js' file in your Genie skin. (The one David set up for you.) That code doesn't make a distinction between the window and the underlying screen -- it loops through all 'button' widgets that are on the current web page (no matter where they are located) and hides them, then creates a menu on the left from them. The result will contain all function keys from both the main display and the window.

This is a copy of our example Hybrid skin, with only small changes (if any?).

I think this could be enhanced to check for windows and only include the top-level window... but, at this point, it doesn't look like it is doing so.

[khoreis]

The F4 was supposed to be on the original and I fixed it today. You mentioned code from Hybrid but I didn't see any.

[Scott Klement]

Kevin,

The code I mentioned is in the custom.js file of your Genie skin.

I hope you understand what I'm saying? That the menu on the left contains all function keys that are currently printed on the screen, it doesn't matter if they are in the window or on the main screen, they'll be listed in the menu on the left -- that's how Hybrid works.

I'm wondering if this is confusing and we should change Hybrid. (and also your skin, to match)

What do you think?

[khoreis]

The problem that I see is that I have a main screen with 10 F-Keys and a Window with 2. How do I know which F-Keys belong to the Window? We have 4 choices:
1. Leave the F-Keys on the Window
2. Adjust the Side Screen to only show the Active F-Keys
3. Adjust the Side Screen to highlight the Active F-Keys
4. Create a Side Screen for the Window

I'm leaning towards 2 or 1, in that order.