Feedback
Did this article resolve your question/issue?

   

Article

Running character application code with V6FRAME, frames are overlayed in GUI

Information

 
TitleRunning character application code with V6FRAME, frames are overlayed in GUI
URL NameRunning-character-application-code-with-V6FRAME-frames-are-overlayed-in-GUI
Article Number000192771
EnvironmentOpenEdge
11.3
Windows
Question/Problem Description
Running character application code with V6FRAME, frames are overlayed in GUI.

In a Windows graphical environment we need to run a character application with character frames.  We use V6FRAME in the form definition.  For example:
 
DEF VAR a AS CHAR LABEL "FIELD A" INIT "12345678".
DEF VAR b AS CHAR LABEL "FIELD A" INIT "87654321".

FORM a WITH NO-BOX SIDE-LABEL FRAME frA ROW 1 V6FRAME.
FORM b WITH FRAME frB ROW 2 SIDE-LABEL V6FRAME TITLE "Campo B".

DISP a WITH FRAME frA.

UPDATE b WITH FRAME frB.

Both frames in character mode are displayed together, but in GUI this code displays the frames one after the other:

User-added image

User-added image


The form frA displays, but the user needs to press a key to display frame frB and frame frA is hidden.

Why does frame frB overlay frame frA when it doesn't in the character client?
 
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Cause
This is expected behavior.  The differences in the border and fonts used by character and GUI environments when compiling the UI widgets, means there isn't enough room to display the frames in the GUI window as the character session does.
Resolution
Use the V6Display parameter in the ini file or registry set to YES.  For example:

[Startup]
V6Display=yes
;ImmediateDisplay=yes
;MultitaskingInterval=100
DefaultFont=MS Sans Serif, size=8
DefaultFixedFont=Courier New, size=8

Running the code with this option results in:

User-added image
Workaround
Notes
References to Other Documentation:

OpenEdge Deployment: Managing ABL Applications, Chapter 4: Maintaining User Environments
Last Modified Date8/4/2016 12:26 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.