When I tab to my autocomplete box, it puts the cursor at the start of the autocompletebox. But this only happens when I set the selected item programatically. When I type it in and then tab back to it, it puts the cursor at the end.
This causes a problem because when I tab and the cursor is at the start, the search text goes blank.
And I can even catch that on a key down.
Everytime I try to do a combobox/autocomplete it takes me about 2-3 days to get it the way I want it. Then I notice some bug that screws everything up.
I think the most common way people want to use a combo/search box is to start typing, catch the first few letters and tab out to the next field. Even that doesn't work. Even when I'm on append mode, when I catch the first few letters and tab out, it just selects the item and keeps the focus on the autocomplete box. Now I can catch this by the keyup also. But then a strange thing happens. If I tab to that autoCompleteBox, it automatically kicks me out to the next tabfield. For some reason it things that I clicked the tab inside the autocomplete control.
Now I saw something was fixed in a WPF autocomplete focus issue recently. I have the latest silverlight 2013.1.403. I'm not sure if it's fixed there or not. I guess it doesn't matter, because I'm just going to use a regular ordinary textbox, and do the filtering and focus on my own.
I've wasted 3 work days on this issue that started from me having to move away from the radcombobox because even when virtualized, a keypress took 2 seconds to register in the combo box. (This was an issue with over 100,000 items)
I think you're trying to add too much to your RadCombo/Autocomplete box. I just want to start typing, see a match, tab out, put the matched value in the textbox
Well I guess I can probably use this to fix the focus.
sender, RoutedEventArgs e)
TextBox ch = FindChild<TextBox>(rc1);