Autocomplete problem

[Blaine Anderson]

Our users use the Autocomplete functionality as follows:
- Start typing
- Use the arrow keys (up/down) to select the desired item.
- Hit the TAB key to move to the next control on the form.

In an earlier version of EssentialTools, the autocomplete would "remember" the currently highlighted item and show it in the edit box when the user tabbed out of the control. This no longer works in 5.1.1.13.

How can I get this behavour back?

-Blaine

[Nandakumar R]

Hi Blaine,

Thank you for your interest in Syncfusion products.

I tried the reproducing steps you have mentioned in the following sample and was not able to reproduce the issue in the version 5.1.1.13.

http://websamples.syncfusion.com/samples/Tools.Windows/F68662/main.htm

Please try the sample and let me know if I have to change anything during the testing of the issue.

I would like to recommend you to use our latest version v5.2.0.25, which is more stable compared to the version 5.1.1.13 and contains important bug fixes and more new feature implementations. Please refer the below link for more details and downloads.

http://www.syncfusion.com/downloads/latestversion/default.aspx

Regards,
Nanda

[Blaine Anderson]

Here is how to reproduce the bug using the Syncfusion examples for Windows forms. Please see the attached screenshot.
- Start the autocomplete sample.
- add the following strings by typing them and hitting enter: aabc, aacd, aafg, aagh.
- type "aa" into the textbox.
- use the arrow keys to select "aagh"
- Hit the Tab key.

The questioon is, how can a make sure that "aagh" shows up in the edit box when the tab key is pressed?

screenshot.zip

[Jeba S]

Hi Blaine,

Thank you for you update and screenshot.

Please refer the Incident 37888 to follow this query.

Regards,
Jeba.

[Jasper]

Hi Blaine,

Thank you for your interest in Syncfusion products.

The issue mentioned here is suspected to be a defect, since it worked fine in the previous version of the Syncfusion product. We have

created a new incident(#37952) for this issue. So please refer that incident to follow this issue.

Regards,
Jasper.