Project

General

Profile

Bug #2783

Bug #2677: fix drawing and functional differences between P2J GUI and 4GL GUI

./window_sizing/create_empty_window.p fails for web and swing clients

Added by Sergey Ivanovskiy over 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Sergey Ivanovskiy
Target version:
FWD - GUI Support for a Complex ADM2 App
Start date:
10/23/2015
Due date:
% Done:

100%

billable:
No
vendor_id:
GCD
case_num:

window_sizing.log Magnifier (1.05 MB) Sergey Ivanovskiy, 11/05/2015 01:36 PM

History

#1 Updated by Sergey Ivanovskiy over 8 years ago

./window_sizing/create_empty_window.p, ./window_sizing/test_runner.p and ./window_sizing/default_empty_window.p fail with open and close circles for the swing client.

#2 Updated by Greg Shah over 8 years ago

  • Assignee set to Sergey Ivanovskiy
  • Target version set to Milestone 12

#3 Updated by Sergey Ivanovskiy over 8 years ago

This program is a test suit with tracing the results to the window_sizing.log file and it doesn't represent a clear visual demo.
Greg, could you help me to run correctly this program on P2j? The readme.txt only describes how to run this tests suit with the Progress 4GL, but not how to run it on P2J. I have checked create_empty_window.p converts "run" statements to the following construction

ControlFlowOps.invokeWithMode("window_sizing/window_positioning_failures.p", "II", hwin, new logical(false));

Thus it doesn't convert window_positioning_failures.p. May be this issue is raised due to not all required procedures are converted.

#4 Updated by Greg Shah over 8 years ago

Thus it doesn't convert window_positioning_failures.p. May be this issue is raised due to not all required procedures are converted.

Yes, this is the issue. You must convert all the window_sizing/*.p files. Then run ./window_sizing/test_runner.p using p2j-entry in the directory (com.goldencode.testcases.window_sizing.TestRunner.execute) or using client:cmd-line-option:startup-procedure=./window_sizing/test_runner.p on the Swing client command line.

#5 Updated by Greg Shah over 8 years ago

Is there a real issue left here or was the original problem just a matter of missing converted code? If there is no known issue, I'd like to close this.

#6 Updated by Sergey Ivanovskiy over 8 years ago

Is there a real issue left here or was the original problem just a matter of missing converted code? If there is no known issue, I'd like to close this.

These testcases aren't failed if all required files are converted, compiled and the complete testcase.jar is build. But it is difficult for me to conclude that these tests are passed or not, because the tests results are in the log file and there is no hint what is expected as a result of the corresponding test. For example, I found these lines in window_sizing.log

window_positioning_failures start                                                                                                                                        
beginning state: ROW = 2.05; COLUMN = 4.4; X = 17; Y = 22; WIDTH-PIXELS = 400; HEIGHT-PIXELS = 462; WIDTH-CHARS = 80; HEIGHT-CHARS = 22; RESIZE = yes; THREE-D = yes;                                                                                                                                         
UNEXPECTED_ERROR: Expected the ROW to be -131072 and found -131070                                                                                                                                                                                                                                                           
UNEXPECTED_ERROR: Expected the ROW to be -131072 and found -131070                                                                                                                                                                                                                                                            
UNEXPECTED_ERROR: Expected the COLUMN to be -131072 and found -131070                                                                                                                                                                                                                                                     
UNEXPECTED_ERROR: Expected the COLUMN to be -131072 and found -131070                                                                                                                                       ending state: ROW = -131070; COLUMN = -131070; X = -655355; Y = -2752491; WIDTH-PIXELS = 400; HEIGHT-PIXELS = 462; WIDTH-CHARS = 80; HEIGHT-CHARS = 22; RESIZE = yes; THREE-D = yes;

#7 Updated by Greg Shah over 8 years ago

  • Status changed from New to Closed

That is an issue, but it is something to be worked in another task. I'm going to close this.

#8 Updated by Greg Shah over 8 years ago

  • % Done changed from 0 to 100

#9 Updated by Greg Shah over 7 years ago

  • Target version changed from Milestone 12 to GUI Support for a Complex ADM2 App

Also available in: Atom PDF