Autocomplete in text fields not working correctly
Moderator: Gurus
Autocomplete in text fields not working correctly
When typing into a drop down box text field (like the genre field) the autocomplete feature should only execute if there is not text to the right of the cursor. In other words as you type your word it should be autocompleting if something matches but not if you are editing in the middle of text already in the field. Currently it will delete all text to the right of the cursor if it finds a match on the text to the left of the cursor.
autocomplete problem
kknostman,
What build of mediamonkey did you find this bug in?
I just tested MM 2.2 RC-1 and couldn't reproduce the problem. I tested with Genre=Rock & Roll, and then tried editing it to Rock/ , but it didn't autocomplete to Rock/Pop.
-Rusty
What build of mediamonkey did you find this bug in?
I just tested MM 2.2 RC-1 and couldn't reproduce the problem. I tested with Genre=Rock & Roll, and then tried editing it to Rock/ , but it didn't autocomplete to Rock/Pop.
-Rusty
Build 1.596 (I believe).
Try this.
1. Have 3 genres: audiobook, audiobook - fiction and audiobook - science fiction.
2. Assign a file to audiobook - fiction.
3. Open properties for this file. Highlight everything after audiobooks ( fiction) and start typing immediately after "audiobooks" so that you can place "science fiction" at the end.
When I do this as soon as I type the space the field autocompletes to "audiobooks".
Hopefully I've explained it properly [/list]
Try this.
1. Have 3 genres: audiobook, audiobook - fiction and audiobook - science fiction.
2. Assign a file to audiobook - fiction.
3. Open properties for this file. Highlight everything after audiobooks ( fiction) and start typing immediately after "audiobooks" so that you can place "science fiction" at the end.
When I do this as soon as I type the space the field autocompletes to "audiobooks".
Hopefully I've explained it properly [/list]
autocomplete problem
I tried this with MM 2.2 RC-1 (build 2.2.1.746), posted in the beta forum, but could not reproduce it. You may want to give this build a try--this issue (and over 100 others) are fixed in this build.
-Rusty
-Rusty