Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <17063751.1186671942654.JavaMail.jira@brutus>
Date: Thu, 9 Aug 2007 08:05:42 -0700 (PDT)
From: "Ilya Berezhniuk (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Commented: (HARMONY-4423) [classlib][awt][jedit]
 Toolkit.getLockingKeyState() is not implemented
In-Reply-To: <26674524.1184161505287.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ilya Berezhniuk commented on HARMONY-4423:
------------------------------------------

With new improved implementation I've got wrong behavior :)
So now I'm trying to locate an issue.

Regarding exception throwing: by the spec, for wrong key these methods should throw IllegalArgumentException, and for headless mode they should throw HeadlessException. So I'll leave exception message as it, and I'll use string in code (not from table), because UnsupportedOperationException will be thrown from native code.

> [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: Alexey Petrenko
>         Attachments: 4423_win.patch, 4423_win.patch, 4423_win.patch, 4423_win.patch, 4423_win.patch, 4423_win_nosearch.patch, 4423_win_nosearch.patch, 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.