Hi
I'm using an UltraCombo (version 9.2). If I keep the DropDownStyle as the default value DropDown, it's shown okay. But if I change it to DropDownList so users can type into it, the top and bottom border disappear when I run the form.
Is this a bug?
Hi,
Which borders are you referring to? The borders on the edit portion of the control or the borders on the dropdown?
Can you post a screen shot? You can attach a file to your post on the Options tab and if you attach an image file, it will display as an image in your post.
Hi Mike
It's before you click on it, is that the edit portion? It only happens when it's disabled. My next post shows it looks okay when it's enabled.
Hi John. The resolution timeline for this issue is 30 business days. Our developers are currently reviewing this case. I'll keep an eye on it and let you know when it has been resolved.
Thanks for the update, Mike.
After telling my manager, he said he's interested in purchasing v10.1 but he wants to know if or when the bug might get fixed. I don't know since I haven't dealt with Infragistic's Developer Support before. Can you give me an estimate?
Thanks, John
A development issue has been logged for this case. The issue number is 66478.
I should've been clearer. It's the UltraCombo with the label 'Package Type' in the bottom half of the screens. The top and bottom edges aren't visible in the top image when the control is disabled.
Hi John,
I'm looking at these two images and straining my eyes trying to see the difference. I can see that the row is disabled in the first image and enabled in the second. But I'm still not sure what border you are referring to.
All of the cells look the same to me in each image.
Which column should I be looking at here?
Okay, never mind, I see it now. You are talking about the Combo at the bottom of the form that says "BOXES" on it.
I just tried this out and I see the same problem. This is clearly a bug.
I'm going to forward this thread over to Infragistics Developer Support so they can check it out. But please be aware that v9.2 is no longer being updated. So any fix for this will only be done in the currently-supported versions: v10.1 and up.