I have some issues with some UltraButtons. My form has an UltraTabControl with two tabs. When I click on an UltraButton on tabpage #2, the selected tab is changed to tab #1 and tabpage #1 is shown. On the same position where this "change my tab"-button is located on tabpage #2 is another UltraButton on tabpage #1. This buttons is disabled all the time, but it gets the HotTrackAppearance when the tab is changed. The button stays with the HotTrackAppearance until it is enabled. I tried to enable the button while changing the tabs and disable it again when the change has completed, but that didn`t work. Even calling button.refresh() doesn`t update the button appearance.
Does anyone know, why the button gets the wrong appearance and how I can fix this behaviour?
Best wishes,ProXy
Hi rootbash...I received your request in Developer Support and I have sent a reply to you through our Customer Help System.
You should submit a small sample project demonstrating this behavior to Infragistics Developer Support so they can check it out. It sounds like a bug to me.
Hi Mike,
the button on tab1 is disabled all the time, I set the button disabled when leaving tab1. But the button still gets the HotTrackAppearance, when chaning back to tab1. It is hottracked and disabled at the same time, moving over the button after chaning to tab1 doesn`t change it`s appearance, because it is disabled..
I just discovered another issue with the ultrabuttons: I have added some drag and drop to some of the buttons, so I can drag a button to another one. When dropping, both buttons change its position. Some buttons have the hottrack apprearance after drag and drop, even the mouse is not one those buttons..
Hi,
When is the button being disabled? It sounds to me like when you click on the button on Tab 2 and it switched to tab 1 that the mouse will be over the button on tab 1, since they are in the same place, so it must be picking up the HotTracking appearance at that point. It's probably caching the appearance and then not recognizing that it is getting disabled afterward.
This sounds like a bug to me and you should try to duplicate it in a small sample project and then Submit an incident to Infragistics Developer Support