Project

General

Profile

Bug #2658

MESSAGE statement expressions that evaluate to a HANDLE are improperly processed

Added by Greg Shah over 8 years ago. Updated over 8 years ago.

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

0%

billable:
No
vendor_id:
GCD
case_num:

Related issues

Related to User Interface - Feature #1790: implement menu support Closed

History

#1 Updated by Greg Shah over 8 years ago

As found by Vadim in #1790 note 519:

MESSAGE MENU-ITEM mi:NEXT-SIBLING. is converted to message(MenuItemWidget.findMenuItemStatic("mi").getNextSibling()); that calls LogicalTerminal.message(handle hWin) method. This method expect that the parameter will be the window handle. I.e. it is treated as MESSAGE "" IN WINDOW hWin statement. But that is wrong. It must be treated as MESSAGE MENU-ITEM mi:NEXT-SIBLING:ID..

I think the majority of the issue is that HANDLE expressions in a MESSAGE statement are implicitly wrapped in a STRING() builtin function when executed in the 4GL.

Also available in: Atom PDF