I put the UltraComboEditor v8.2 in windows forms in VS 2005. If there is no items in the UltraComboEditor at runtime,i click the arrow button in that control, then it appears like small white square space below the control.This problem occured after Upgrade Infragistics v6.1 to v8.2 . how to resolve this problem.
I'm not sure I follow you. What's the problem? What do you want to happen?
Isn't is a bit confusing for a user to click on a dropdown button and have nothing (or an empty list) show up?
Hi,
1.I put one UltraComboEditor v8.2 in windows forms in VS 2005.
2. i did not add any item to that control.then run the application.
3. While clicking Dropdown button in UltraComboEditor v8.2, it shows small white square space below UltraComboEditor v8.2.
How to resolve this Problem?
Well... I'm still not sure what you want or expect to happen here. It sounds to me like the little white square is an empty dropdown list. If you want to prevent that, I suppose you could handle the BeforeDropDown event and cancel the event if there are no items on the list.
Thank you for your information. Now i can able to prevent that little white square while cancel the BeforeDropDown event. But Our problem is
1. Previously we are using the Infragistics v6.1 for our project. At that time, there is no little white square appear below the UltraComboEditor Control when there are no items on the list.
2. Last week,we upgraded to Infragistics v8.2 .After that we got problem like little white square appearance. User do not want this appearance.
3.We have more than 200 UltraComboEditor Controls available in our project.
4. Do you think we need to fire 200 BeforeDropDown event ? it may be affect our performance as well as Coding duration.
Handling BeforeDropDown should not affect performance. And I imagine most of your combos have items on the list, so you would only have to do this for a few that have no items.
I'm not sure what else you can do, though. If the behavior of the control changed from one version to another, you might want to Submit an incident to Infragistics Developer Support. Maybe this could be classified as a bug and fixed in a future release.