This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 21011 - Unable to type extended character in JTextField
Summary: Unable to type extended character in JTextField
Alias: None
Product: qa
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@qa
Depends on:
Reported: 2002-02-28 14:43 UTC by Honza Firich
Modified: 2011-02-17 09:30 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Proposed fix and examples. (4.95 KB, application/octet-stream)
2002-04-05 06:04 UTC, Jiri Skrivanek

Note You need to log in before you can comment on or make changes to this bug.
Description Honza Firich 2002-02-28 14:43:30 UTC
When tried to type extended character in JTextField, jemmy threw an exception.

JTextFieldOperator textField = new JTextFieldOperator
(containeroperator, "text");
textField.typeText("\u010d"); // č

When I used setText method, it worked fine. But I need typeText because I try 
to simulate users input.
I tried this in robot mode as well, but nothing was typed. Is it correct?
Comment 1 Honza Firich 2002-02-28 14:45:30 UTC
        at java.lang.Class.getField0(Native Method)
        at java.lang.Class.getField(
        at com.sun.jemmy.ClassReference.getField
        at com.sun.jemmy.DefaultCharBindingMap.getCharKey
        at com.sun.jemmy.operators.Operator.getCharKey
        at com.sun.jemmy.operators.ComponentOperator.typeKey
        at com.sun.jemmy.operators.JTextComponentOperator$1.launch
        at com.sun.jemmy.ActionProducer.launchAction

Please see also Issue 18866
Comment 2 Alexandre Iline 2002-03-07 11:00:57 UTC
Chars are typed by modifiers and keys pushing. Mapping between chars 
and modifiers/key codes is performed by current CharBindingMap 
implementation which is defined by 
JemmyProperty.setDefaultCharBindingMap(CharBindingMap) method.
Default CharBindingMap implementation (DefaultCharBindingMap) 
provides modifiers and keys only for regular chars: 

Since you are going to reproduce user input, you, probably know both 
modifiers an key code.

Depending of you need, you have two choices:
1. define you own or extend default CharBindingMap
2. Post necessary events by ComponentOperator.typeKey(int, char, 
int) method

If it is a regular simbol, please specify what it is and I'll add it 
to default CharBindingMap.

Comment 3 Alexandre Iline 2002-03-08 11:46:01 UTC
Either new CharBindingMap implementation should be created or 
ComponentOperator.typeKey(int, char, int) method should be used to 
type any char which is not common. All those common chars are 
covered by default CharBindingMap implementation.
Comment 4 Jiri Skrivanek 2002-04-05 06:03:16 UTC
I have experimented with key events and Jemmy on Japanese locale and
found a solution which could be accepted. All examples are done on
Solaris in Japanese locale (EUC).

If you bind a KeyListener to a JTextField and type a Japanese
characted manually, following events are genereated:



Another example:


Key sequence: CTRL+SPACE, N, I, H, O, N, G, O, SPACE, CTRL+SPACE

If you want to simulate such input in current Jemmy, you must use

| JemmyProperties.ROBOT_MODEL_MASK);
        oper.pushKey(KeyEvent.VK_SPACE, InputEvent.CTRL_MASK);
        oper.pushKey(KeyEvent.VK_SPACE, InputEvent.CTRL_MASK);

To be honest, using Robot is only way how to simulate users input
exactly. But to enable use Jemmy to input extended characters in
non-robot mode, I suggest to fix DefaultCharBindingMap.getCharKey() to
return VK_UNDEFINED key code for not known characters. Then you can
write in Jemmy (without robot):

        oper.typeKey('\u3042'); // Japanese unicode char (CTRL+SPACE,
        oper.typeKey('\u010d'); // Czech unicode char
        oper.typeKey('??');	// ?? stands for native char
        oper.typeText("\u010d  \u3042  ??");

Events fired on JTextField for \u3042 are following:


Compare to event listings done "manually" it seems similar. I think
that KEY_TYPED event is the most important. In "NIHONGO" example, no
KEY_PRESSED and KEY_RELEASED events for N, I, H, ... were generated on
JTextField. So such fix could satisfy users testing on non-English

See attachments for suggested fix and examples.
Comment 5 Jiri Skrivanek 2002-04-05 06:04:18 UTC
Created attachment 5303 [details]
Proposed fix and examples.
Comment 6 Alexandre Iline 2002-10-23 02:40:54 UTC
DefaultCharBindingMap class should, definitely, be changed.

However, I doubt it would make any sense to reduce control level 
there if a user would have a possibility to extend this class

I think it would be enough to allow users to extend this class and 
control everything there.

So, what I would do is:

1. replace arrays with Hashtable (or Vector)

2. make those Hashtable protected, so they could be accessed from 
a subclass.

3. add a constructor to DefaultCharBindingMap:
public DefaultCharBindingMap(<hashtable or vector>)

4. implement protected methods:
protected getCharKeyPrimitive(char) throws NoSuchFieldException, 
protected getCharModifiersPrimitive(char) throws 
NoSuchFieldException, IllegalAccessException;

5. make DefaultCharBindingMap Outputable, so those exceptions
would be printed into correct output stream.

After those changes, no metter if user wants to solve problem 
partially or completely, it would be quite easy to add new 
symbols support and exception handling simply by extending 
DefaultCharBindingMap and overriding some methods (changing some 

Does it make sense?

Comment 7 Jiri Skrivanek 2002-10-24 10:15:44 UTC
Seems to me too complicated for users. Additionally, I am not sure if
a mapping is possible for Japanese characters where one unicode char
is mapped to several keystrokes.
Please, give an example what user has to do to be able to use
following code:

oper.typeKey('\u3042'); // Japanese unicode char (CTRL+SPACE, A,
Comment 8 Alexandre Iline 2002-11-11 00:36:26 UTC
DefaultChaBindingMap class has been refactores in 2.1.0

Chars now stored in a hashtable, there are new methods allowing
to "customize" char map by adding or removing chars.

No exception is thrown even if no binding was found for a char:
getCharKey(char) simply returns KeyEvent.VK_UNDEFINED in this