Project

General

Profile

Bug #11053

DATETIME-TZ FILL-IN crashes in VALUE-CHANGED trigger

Added by Vladimir Tsichevski 7 months ago. Updated 7 months ago.

Status:
WIP
Priority:
High
Assignee:
Vladimir Tsichevski
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
16323
version_resolved:
reviewer:
production:
No
env_name:
topics:

Related issues

Related to User Interface - Bug #10706: Date FILL-IN: Unintended VALUE-CHANGED Event Triggered by BACKSPACE WIP

History

#1 Updated by Vladimir Tsichevski 7 months ago

Run the following 4GL example in FWD:

DEFINE VARIABLE f1 AS DATETIME-TZ.
DEFINE FRAME fMain f1.
ENABLE ALL WITH FRAME fMain.
ON VALUE-CHANGED OF f1 DO:
   MESSAGE "Value-changed".
END.
WAIT-FOR WINDOW-CLOSE OF CURRENT-WINDOW.

This creates and enables a DATETIME-TZ FILL-IN widget with a VALUE-CHANGED trigger.

Enter any digit (e.g., 0) into the widget.

The client crashes or restarts with a NumberFormatException caused by Integer.parseInt("+").

#2 Updated by Vladimir Tsichevski 7 months ago

  • Related to Bug #10706: Date FILL-IN: Unintended VALUE-CHANGED Event Triggered by BACKSPACE added

#3 Updated by Vladimir Tsichevski 7 months ago

  • Status changed from New to WIP

#7 Updated by Vladimir Tsichevski 7 months ago

To resolve this issue, changes to datetime and datetime-tz FILL-IN widgets must be applied, mirroring the fix implemented for date in #9846.
The #9846 branch must be merged into trunk first before proceeding with these changes.

Also available in: Atom PDF