Kbase P147998: Escape sequences (tab, return and escape) are not routed correctly if .NET is activated
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
08/09/2009 |
|
Status: Unverified
SYMPTOM(s):
Escape sequences (tab, return and escape) are not routed correctly if .NET is activated
When .NET is activated and the customer's OCX is not:
ESC - not received by any OCX, RichTextField box disappears.
F1/F2 - ok
TAB - not received by any OCX.
ENTER in the customer's OCX: .NET AccessViolationException
When .NET and the customer's OCX are activated:
ESC - (should fire END-ERROR of frame) not fired on the customer's OCX,fired only after another event (e.g. move the mouse)
F1 - ok
F2 - fired only after another event (e.g. move the mouse)
TAB - does not circle (gets stuck on last control).
ENTER - (should fire RETURN of frame) on RichTextField : fired only after another event (e.g. move the mouse); on the customer's OCX: .NET AccessViolationException
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt
When is activated and no OCXs are in use:
ESC - nothing happens
CTRL+O - nothing happens
FACT(s) (Environment):
Using richtx32 OCX
Using customer's OCX, which just lists all the KeyDown events
Using WAIT-FOR System.Windows.Forms.Application:RUN([form-object-ref])
The problem is not observed when .NET is not activated
Windows
OpenEdge 10.2A
CAUSE:
Bug# OE00185024
CAUSE:
Bug# OE00185732
FIX:
Upgrade to OpenEdge 10.2A02