Gen Navigation Diagram design not showing expected Window fields

Products

• Gen
• Gen - Workstation Toolset

Issue/Introduction

When opening an Application Window for updates within the Gen 8.6 Navigation Diagram, none of the existing fields show on the Application Window.  The Application Window appears blank with the exception of menu items and the toolbar display, where are the fields? 

Environment

Gen Toolset

 

Cause

One common cause for this result is that the Application Window within the Navigation Diagram was designed or modified on a dual monitor developer environment. 

Resolution

The field/window objects do exist, they are located at coordinates on the Application Window well off the portion of the Application Window displayed in the Navigation Diagram, within the Toolset.   

To find the Application Window objects, open the Toolset, Navigation Diagram and the Application Window in one monitor.  Next, drag just the Application Window to the second monitor that may be of different resolution.   Make the Gen designed Application Window as large as possible to see if it will show the mapped objects.  Gen developers may need to adjust the monitors resolution scale (i.e. to 100%) to see the Application Window objects.  If the mapped Application Window objects can now be seen, drag the Application Window back to the Toolset and Navigational Diagram monitor, adjust the sizing and save the model on the Toolset monitor.  

Note:  We have Gen utilities available to determine the coordinates of the non-visible Application Window objects such as the Encyclopedia utility Walkency, the Toolset utility IR Command Processor, and the Gen Studio component utility Model Explorer.  The utilities IR Command Processor and Model Explorer are only available if you have the Support Option license key installed.  Please contact Gen Support regarding use of these tools. 

Recommendation:  We recommend to stay within one monitor going forward for developing, building and testing Gen applications.  If wanting to develop Application Windows on a second monitor,  either have the Toolset Navigation Diagram on that same monitor, Or drag the designed Application Window back to the monitor containing the Toolset Navigation Diagram before saving the model. Also, we recommend the deployed user workstation displays be at the same or as near as possible to the resolution of the developer workstations.   

It is acceptable to design the Application Window on another monitor, but that Application Window should always be moved back to the monitor where the Navigation Diagram and Toolset reside before saving the model.  This will prevent the issue reported in this article. It will also prevent problems if not all developers have the same monitor layout or if a developer does not have a multi monitor environment available (e.g., when using only a laptop).

Also, reference the following KB article for additional details along with monitor configuration examples discussed above:

Window/dialog boxes not visible after opening in Window Navigation Diagram 

Note:  Another option from the above steps would be to delete the Application Window and remap the objects using a one-monitor workstation.  If this is done, it would be suggested to setting the common edit modifications option to 'On', this would allow developers to change modes (Windows, HTML, and ASP.Net) and see the objects in all three modes creating less overhead.