Kbase P139755: 4GL/ABL: LEAVE trigger fires inappropriately, may leave random characters on the screen
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
25/06/2009 |
|
Status: Verified
SYMPTOM(s):
4GL/ABL: LEAVE trigger fires inappropriately, may leave random characters on the screen
4GL/ABL: LEAVE trigger fires inappropriately, may leave garbage characters on the screen
When a user defined event "U3" is applied, a LEAVE event trigger of a widget that was not really left also fires.
Sometimes stray characters are left behind in the widget, and the cursor is left at the end of the widget instead of the beginning.
FACT(s) (Environment):
OpenEdge 10.1C01 Service Pack
OpenEdge 10.1C02 Service Pack
OpenEdge 10.1C03 Service Pack
OpenEdge 10.1C 32-bit
OpenEdge 10.1C 64-bit
OpenEdge 10.2A
UNIX
Linux
CAUSE:
Bug# OE00179652
CAUSE:
This issue, which occurs under all AIX, UNIX, LINUX and Windows character clients, has been reported for different variations and in several flavors under the following five separate bug reports. These bug reports were deemed duplicates of each other.
a. OE00181109 - Incorrect events may be generated when a fill-in loses focus when events are programmatically applied to the fill-in in response to the ENTRY or LEAVE events.
b. OE00182536 - GO-trigger is fired when it should not with 10.1C character client on Windows (GUI client works correctly) and on UNIX.
c. OE00179652 - When a LEAVE event fires for a fill-in, the fill-in may display a corrupted value. This is more likely to occur when events are applied to the fill-in programmatically.
d. OE00178499 - Fields displayed on-screen may be replaced by strange characters if a trigger APPLYs an event to itself without using RETURN NO-APPLY afterward.
e. OE00180308 - In a character client, when entering a numeric value in a field which has APPLY ENTRY in the LEAVE trigger, this value will disappear when pressing TAB to leave the field.
FIX:
Upgrade to OpenEdge 10.1C04 or later or to OpenEdge 10.2A01 or later