Project

General

Profile

Bug #9343

Incorrect NEXT-SIBLING attribute value for child WINDOW widget in GUI mode

Added by Eugenie Lyzenko over 1 year ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
trunk rev 15561
version_resolved:
reviewer:
production:
No
env_name:
topics:

History

#2 Updated by Eugenie Lyzenko over 1 year ago

The problem description. In GUI mode it is possible to have child window widget alongside with frame widget inside the same parent window. In this case for child window FWD reports incorrect value for NEXT-SIBLING attribute. The sample:

default-window:visible = true.

def frame f.
enable all with frame f.

message default-window:next-sibling:type.

def var h as handle.
create window h assign parent = default-window.
view h.

def frame f2.
enable all with frame f2 in window h.

message h:next-sibling:name. /* this prints the f and not f2 */

This sample running in 4GL shows f as next sibling for child window. While in FWD the sibling is f2. This is not correct and need to be fixed.

Also the converted code for message default-window:next-sibling:type. gets the errors in FWD so this is another bug here. Seems like NEXT-SIBLING for single root window should be the window itself, not null or Unknown handle. So seems like this should be fixed as well.

Only GUI mode is valid for this testcase. For ChUI it is not possible to have child window.

Also available in: Atom PDF