[HARMONY-4423] [classlib][awt][jedit] Toolkit.getLockingKeyState() is not implemented

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: App-Oriented Bug Reports, Classlib
• Environment: Win32
• Patch Info: Patch Available
• Assignee: Alexey Petrenko
• Reporter: Vasily Zakharov
• Created: 11/Jul/07 13:43
• Updated: 21/Aug/07 14:09
• Resolved: 14/Aug/07 08:15

Description

Method java.awt.Toolkit.getLockingKeyState(int) is not implemented and throws RuntimeException when called. This prevents some applications like jEdit automated GUI test scenario from running normally, see HARMONY-3633, it had to provide a special workaround patch to address this issue.

Implementing this method may be tough as it requires writing native code, however a simple workaround patch may be created to improve compatibility while the real implementation is absent. Here I provide this patch (actually extracted from HARMONY-3633) and my suggestion is to apply it immediately.

Issue Links

• is related to: HARMONY-3633 [testing] JEdit automated GUI test scenario for B&T 2.0 infrastructure
• relates to: HARMONY-4635 [classlib][awt] Toolkit.setLockingKeyState() is not implemented on Linux
• relates to: HARMONY-4636 [classlib][awt] Toolkit.getLockingKeyState() is not implemented on Linux
• relates to: HARMONY-4503 [classlib][awt] Toolkit.setLockingKeyState() is not implemented
• relates to: HARMONY-4659 [testing] JEdit automated GUI tests use obsolete workaround for java.awt.Toolkit