Kbase P176599: ABL .NET application generates errors 5897 and 4123 and then crashes
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
02/11/2010 |
|
Status: Unverified
SYMPTOM(s):
ABL .NET application generates errors 5897 and 4123 and then crashes
Input blocking statement is invalid in trigger: <event trigger procedure>. (5897)
None of the widgets used in the WAIT-FOR statement are in a state (such as SENSITIVE) such that the specified event can occur. WAIT-FOR terminated. (4123)
Application tracks and stores missed mouse clicks
Missed mouse clicks are processed by PROCESS EVENTS
Some events do a WAIT-FOR GO
FACT(s) (Environment):
OpenEdge 10.2B
Windows
CAUSE:
Whilst processing an event, PROCESS EVENTS can cause a second event to fire. Since the AVM is already processing the first event, it cannot allow any blocking statements to execute, hence the errors.
PROCESS EVENTS is really meant to be used in scenarios where long processing loops take place and want to allow windows to paint or some action to execute as soon as possible while in that long/tight loop. Howeverm this should not be necessary in an event handler.
FIX:
Remove PROCESS EVENTS