SuggestionViewHeight behavior

[Paul]

Not super important.. but it bugs me that I don't understand it..

 

Given a list of states as the source for Autocomplete,

 

With S I get South Carolina and South Dakota

http://puu.sh/AMw1S/6e7248fdb4.png

 

But with T I get only Tennessee and not Texas?

http://puu.sh/AMw2K/80575a80c0.png

 

I have to go all the way to Tex before I see Texas?

http://puu.sh/AMw3n/a7c1213eb6.png

[Pavel R. Pavlov]

Hi Paul,

I tried to reproduce the reported behavior on our side with our latest official release to no avail. The AutoComplete suggested 2 items when I entered "T". You can see the exact behavior in the attached GIF file.

Maybe I am missing something and my setup does not fully reflect yours. This is why I am providing the solution I created to test the behavior. I would like to kindly ask you to try to match your setup as closely as possible and if you can consistently reproduce the behavior, send the solution back. This will greatly help us in investigating the reasons behind the behavior.

However, if the described behavior bothers you and you want to change it, you could try setting a threshold for the entered symbols. This can be done by setting the SearchThreshold property. Please give this a try and let me know if it is good enough for you.

I`m looking forward to hearing from you.

Regards,
Pavel R. Pavlov
Progress Telerik

[Paul]

I agree your sample seems fine.

I changed it a bit to match the use model I had.. Mainly I was using ViewModel binding and the model was a POCO with fields.

I now have two autoComplete fields now to demonstrate the apple/orange behavior.

 

The first binds to the ViewModel.Source which is just a List<string> and this works, just as your example works. Start with T and I get Tennessee and Texas.

 

The second binds to ViewModel.States which is a List<States> and the autoComplete is told to search the Name field.. the Name field dataset is identical to the Source list of strings.  But the behavior is different now. start with T and you get only Tennessee. Search for Tex and you see Texas.

I also noted in simplifying the case to remove everything but tennessee and texas... the behavior then matches the first autoComplete.. Only when I add more data.. it starts to behave differently.  So I didn't simply the dataset.

 

O.. I'm not allowed to attach the zip files.

MainPage.cs https://pastebin.com/3AeXpGvz

MainPage.xaml  https://pastebin.com/0KQs2FL0

 

[Paul]

o.. and its the UWP version that does this btw.

the Android version seems fine.

[Pavel R. Pavlov]

Hi Paul,

Thank you for providing additional information about the specifics of your setup. Indeed with the TextSearchPath property set the UWP RadAutoComplete behaves differently from the Android component. This is why I logged a bug report in our feedback portal. If you follow it you will receive notification whenever we update it.

For the time being as a workaround I would suggest setting the SearchThreshold property as described earlier. This will change the behavior of the component.

As a small sign of appreciation of your contribution I updated your Telerik account.

Regards,

Pavel R. Pavlov
Progress Telerik