Bug #2658
MESSAGE statement expressions that evaluate to a HANDLE are improperly processed
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
Related issues
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 tomessage(MenuItemWidget.findMenuItemStatic("mi").getNextSibling());
that callsLogicalTerminal.message(handle hWin)
method. This method expect that the parameter will be the window handle. I.e. it is treated asMESSAGE "" IN WINDOW hWin
statement. But that is wrong. It must be treated asMESSAGE 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.