Fusion errors

[Theo Kusters]

Hi,

I have some issues with Fusion. See: ACS vs Fusion.docx
The bottom line (not a message line) isn't shown
The option field and the first positions of the subfile aren't shown.
The PSHBTNFLD/PSHBTNCHC options in the header aren't processed

After pressing F3 the cursor remains in the last position of the previous screen not in the first input capable field.

Sometimes the cursor isn't in the correct position and hard to find, Please add the option for a block cursor.

Kind regards,
Theo

[richard.milone]

Can you confirm the Valence version you're running?

[Theo Kusters]

Yes, sure, that's : 6.0.20210226.1

[richard.milone]

Could you email the DDS for that screen in a SAVF to support@cnxcorp.com?

[Theo Kusters]

Mailed it as requested.

[richard.milone]

Please update to Valence 6.0.20210322.0 and check that screen again in Fusion5250. At a minimum the function keys should show along the bottom and the rendering of the option column on the left should be correct now. Some other cosmetic improvements will come out in the April release.

[Theo Kusters]

Hi Richard,

Thanks for the update. All the data on the screen is displayed now. Remaining issues:

• PSHBTNFLD doesn't function yet
• SFLSNGCHC(*RSTCSR *AUTOSLT) doesn't display in RI
• Using F3 to return to previous screen doesn't position the cursor in the first input capable field.

Using Fusion on a iPad we have some other problems:

• The tab key from the onscreen keyboard doesn't work
• Starting Fusion leads to the error message "Error communicating with ws://hostname:17052" while fusion is running on 18052 (It works fine in the browser)
• The subfile option in display file ART400D (see mail) doesn't show
• In a popup window with only Enter and F3 enabled in can't enter or use F3. Only option is to signoff.

Regards,
Theo

[richard.milone]

Regarding the remaining issues, we are preparing a feature in the next Valence build that will allow you to gather 5250 data stream info for us to debug easier. It should be out by early next week. I'll follow up with you again when it's ready and with further instructions.

[TerryB]

Richard, just a note here I'm still seeing a similar symptom to what Theo describes when using F3 to return to previous screen. When I send a popup Window (not a full screen, the Window keyword in use) Fusion is still not setting the cursor position in the popup window all the time. Sometimes you can still see the cursor sitting on the field on screen behind the popup. But of course it has no focus to do anything. Guys have to click in field on the new popup screen.

Now, it is easy workaround that I've been doing when guys tell me about one. All I have to do is go to DDS of popup window and specify Position Cursor on one of fields. You guys looked at this with me when Fusion was first out but it has not gone away yet.

[richard.milone]

TerryB:
The next build of Valence 6 will have a debug mode for Fusion5250 that allows you to "record" the 5250 data stream and email it to CNX for analysis. This will allow us to then fix the problem. The next build should be out sometime this week.

[Theo Kusters]

richard.milone

In this case I select option D in a subfile that displays some choice fields and F12 in a WINDOW.
In Fusion the cursor remains in the background, the choices can't be selected and F12,defined in the WINDOW, doesn't function.
See attached log

[Theo Kusters]

richard.milone

In this case I select option 2 in a subfile that displays some choice fields (SFLSNGCHC(*RSTCSR *AUTOSLT) ) and F3/F5/F12 in a WINDOW.

In Fusion the cursor is in the window but not restrained to the window,
the choices arn't in RI

The function keys are working in this case.

See attached log

[Theo Kusters]

And a request:

Please make it possible to show a block cursor. Sometimes the cursor is hard to find.

[richard.milone]

Theo Kusters:
Thanks for the debug info. In order for the debug info to be useful, you'll need to start the debug prior to navigating to the base background screen. Can you please redo the debug sessions from an earlier starting point and repost?

Also, please start a new forum post thread for each issue/question/recommendation individually so that we can better track them.

Regarding the block cursor, we have looked at this numerous times and have yet to find a way to do it effectively. The cursor you are seeing is rendered by your browser, not by Valence. CCS can control its color but little else. In order to render a block cursor we would need to do some sophisticated tricks to disappear the existing cursor, quickly draw a synthetic replacement, and then try to keep that replacement positioned correctly during every possible cursor movement. So this type of cursor isn't in the plan currently, but if you find any browser app or examples that use a block cursor effectively, please send along to us for analysis. We so far have not found one.

[richard.milone]

TerryB:
We now have the ability to collect debug info needed for fixing visual and functional Fusion5250 issues. If you update to the latest Valence 6 (6.0.20210421.0), you can then use the debug feature in Fusion5250 to record the 5250 data stream. Then you can send that debug info to CNX for analysis. Look for the debug button in the lower left corner, and be sure to start the debug session before navigating to the first screen where the problem occurs. Also be sure you fully explain the expected behavior. Comparison screen shots between Fusion5250 and ACS on your system are always very helpful to include so we can fully understand the expected behavior.