Entering values in "Change values?" box

[maarten]

With the latetest (08-07-2007) JOSM, when you enter data in the change values box, JOSM jumps to the first item that is in the dropdown list when you type a character. But when you type a second character, JOSM jumps to the item that starts with that charcater. That is very annoyinh. JOSM has to jump to the item that starts with the two charcaters you type.
Or when there is no value that starts with that character, JOSM deletes the first and shows only the second character.

This is especially very annoying when typing in names. Example highway names:
names list holds: A50, A67
I want to enter A73 for a new way.
I type A, JOSM highlights A50;
I type 7, JOSM shows only 7;
I type 3, JOSM shows only 3.

This is really annoying. The selection of the first value in the list is a good option, but deleting characters that were already typed is bad.

[Firefishy]

I too find this bug annoying. The selection should not be the entire entry after first key, it should be the remainder of the text.

I am running Sun JRE 1.6.0.2 on a WinXP box.

I am going to try an older version of the JRE.

[anonymous]

Replying to josmbug@firefishy.com:

I am going to try an older version of the JRE.

Same problem on 1.5.0.12. After first key, the entire selection is highlighted, following key replaces the entire field.

[Firefishy]

My no-idea-what-I-am-doing fix.

Index: src/org/openstreetmap/josm/tools/AutoCompleteComboBox.java
===================================================================
--- src/org/openstreetmap/josm/tools/AutoCompleteComboBox.java  (revision 314)
+++ src/org/openstreetmap/josm/tools/AutoCompleteComboBox.java  (working copy)
@@ -55,7 +55,6 @@
                                editor.setSelectionStart(offs + str.length());
                                editor.setSelectionEnd(getLength());
                        }
-                       setSelectedItem(item);
                }

                private void setSelectedItem(Object item) {

[anonymous]

This bug was happening for me too. It only happened with the Windows Look and Feel. Switching back to the Metal look and feel solved the issue for me.

[anonymous]

Fixed in r736.