harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Petrenko (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-4423) [classlib][awt][jedit] Toolkit.getLockingKeyState() is not implemented
Date Mon, 30 Jul 2007 06:07:53 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516288
] 

Alexey Petrenko commented on HARMONY-4423:
------------------------------------------

So what are the problems from Windows API and Linux API sides which are prevents us from getting
the state of CAPS, NUM, SCROLL and KANA LOCK keys?

> [classlib][awt][jedit] Toolkit.getLockingKeyState() is not implemented
> ----------------------------------------------------------------------
>
>                 Key: HARMONY-4423
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4423
>             Project: Harmony
>          Issue Type: Bug
>          Components: App-Oriented Bug Reports, Classlib
>            Reporter: Vasily Zakharov
>            Assignee: Alexei Zakharov
>         Attachments: Harmony-4423-Workaround.patch
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message