I have built my own on screen keyboard control.  I used UltraButtons and set the AcceptsFocus to false so I don't hava a problem with focus.  I have everything working well but the auto complete with suggest.

I switched the references to the version I am using.

I tweaked your example.  If you run it,

1. Click on "A" it will put the A in the combo fine. 
2. The drop down will open for the auto complete suggest
3. Click on "P"
4. The suggestions will close and there will not be a "P" in the combo box
5. Click on "P" again (2nd time)
6. The "P" will be added to the combo so it now is "AP"
7. The drop down will open
8. Click on "P" (3rd time)
9. The suggestions will close and there will not be a 2nd "P" in the combo box
10. Click on "P" again (4th time)
11. The "P" will be added to the combo so it now is "APP"

I expect the the P to be added to the combo box the first time the button is clicked.  I have tried all sorts of things like sending the P twice each time its click, but that doesn't work either.

Thanks

1. Click on "P"
2. The suggestions will close and there will not be a "P" in the combo box
3. Click on "P" again
4. The "P" will be added to the combo so it now is "AP"

Hello,

Thank you for following up and clarifying things. I now understand the behavior your describing with the DropDown closing up when you don't want it to. From my understanding this is to be expected. I am currently in a discussion with my team to figure out a viable approach for your requirement.

To clarify, regardless of what is clicked on your OSK (on-screen keyobard) and/or form, the dropdown closes by simply clicking the away from the editor which is to be expected. Forcing it open and controlling the focus may result in unexpected behavior.

Let me know if you have any questions regarding this matter and I will follow up with or results by the end of the day tomorrow.

I believe they combo works perfectly using a physical keyboard.  I want to be able to simulate that exact same functionality using SendKeys

I would expect it to work this way:

1.  Press "A" button

2.  The combo text would be "A"

3. The combo opens with "A" suggestions

4.  Press "P" button

5. The combo text would be "AP"

6. The combo opens (or remains open) with "AP" Suggestions

7.  Press "P" button

8. The combo text would be "APP"

9. The combo opens (or remains open) with "APP" Suggestions

I want to use sendkeys to mimic they way the physical keyboard works.

Thanks

Hi,

Just to expand a little bit on what Mike said... I tried out the same thing you are doing here using the AutoComplete functionality of the inbox ComboBox control.

With the ComboBox, the first click of the "P" button behaves the same way as UltraComboEditor. The suggestion list drops down and everything works fine.

The second click on the "P" button behavior different. With the ComboBox, what happens is that the click of the button closes the dropdown. That part is the same.

The differece is that the UltraComboEditor eats the mouse message since it is using that mouse message to close the dropdown. So the click event of the button never fires.

The ComboBox, on the other hand, responds to the mouse message (by closing the dropdown), but it does not eat the message. It allows the message to continue to be processed, so the click event of the button fires. This causes the Combo's suggestion list to drop down again.

So even with the ComboBox, you can see the list close and then re-open.

Note that this only happens with the AutoComplete functionality. If you actually drop down the ComboBox's list yourself, it responds the same way UltraComboEditor does - it eats the mouse message.

So we are going to look into this and see what we can do about matching the same functionality as the ComboBox.

Do you have any rough estimate when the change will be released to the world?

Hello,

We are in the beginning stages and your request is under review and currently do not have an ETA. Your private case will be updated automatically when updates are made. In the meantime, feel free to update your case with any questions or concerns that you may have.

Sincerely,

Michael Di Filippo
Developer Support Engineer
Infragistics, Inc.
www.infragistics.com/support

Hi,

We're looking into this issue and I have a question about the needs of your application.

The way the inbox control works is that they always close the dropdown when you click something outside of the control, but they do not eat the mouse message. This means the inbox control closes and then immediately re-opens when you send the key to it.

We could do that, also, but it seems less than ideal. I think what you really want here is a property on the UltraComboEditor to simply tell it not to close up in response to the mouse clicking outside the control.

The advantage of this is that the control doesn't close up and then reopen, it just stays open.

The down side is that you might have to force the dropdown to close in some cases where you want it to. For example, the dropdown would still close when the control lost focus. But if you clicked on some other control (like a toolbar button) that doesn't take focus, it would remain dropped down. You could, of course, handle the ToolClick event and close the dropdown yourself.

The first approach makes things easier, but is not really ideal in terms of the behavior. The second approach means a little more work, but it gives you more control.

What do you think?

Hello,

Issue "184182: With AutoCompleteMode set to Suggest, mouse clicks are not fired" has been addressed in service release versions WinForms_14.1.20141.2097, WinForms_14.2.20142.2034.

This service release is now available under your account at the Infragistics Website. To download the service release, log in to ‘Account’ and select ‘Keys & Downloads’. Select the appropriate tab for this product; then the license key. The available service releases (Hot Fixes) should now be listed on the page.

Let me know if you have any additional questions regarding this matter.

I gave this a try.  It works as expected if the combo auto complete is set to suggest.  If you change it to Suggest Append, then the append is triggered prematurely.  

Is there an easy work around for this?

Thanks

btw, I am the same person as above, the license keys were under a different support login, so I had to use it. :)

Hello,

Can you please clarify the peformance issue?

What I have found is that this is not related to the most recencent fix we provided to you and it applies to Suggest and SuggestAppend Autocomplete options.

The very first time you use the ComboEditor, the dropdown portion open slightly after (milliseconds) the value appears in the textbox. However clearing the textbox and entering the same value shows the suggest feature and the dropdown in sync with eachother.

Thus the issue can only be reproduced once with either typing or sending a key press.

Let me know if this is an accurate assumption and have any additional questions regarding this matter.