I am using 2008v2. I have set the ExplorerBar's ActiveAppearance and I also handle its ClickEvent. I have noticed that I can make an item's ActiveAppearance happen (click to the right of the item itself, not on its center) and it will assume the associated ActiveAppearance but the event is not triggered.
It's very confusing. The ActiveAppearance tells the user that he has clicked that Item when in fact the event was not triggered.
Infragistics.Win.Appearance activeItemAppearance = new Infragistics.Win.Appearance();
activeItemAppearance.BackColor = System.Drawing.Color.FromArgb(192, 255, 192);
ultraExplorerBar1.ItemSettings.AppearancesSmall.ActiveAppearance = activeItemAppearance;
Is it supposed to work this way?
Thanks, Lars
No, I was not able to reproduce the behavior you describe here using a simple sample project. If you are able, attach the one with which you are able to observe this problem and we will take a closer look.
Brian,
I would appreciate a response to this issue.
Thanks for the response, Brian.
Yes, I am handling the ItemClick event. The UltraExplorerBar's Sytle of Control is set to Explorer and the Style of Item is set to Default.
When I launch the app and hover over an item's text, the cursor changes to a hand the the text is underlined, implying a hyperlink. When I move just to the right of the text but still within the boundaries of the control's group, the cursor changes to the standard pointer and the text is no longer underlined.
If I left click at this point, the color I set for ActiveAppearance appears around the text and the text for that item is surrounded with a dotted box. However, the ItemClick event is not triggered. Confusing!
Can you see this behavior?
Assuming that by 'ClickEvent' you are referring to the ItemClick event (and not, for example, the 'Click' event), I was not able to reporduce the behavior you describe here with a simple test. Using the 'ExplorerBar' setting for the Style property, anytime an item was activated the ItemClick event followed on the release of the mouse button.
If you are by chance referring to the control's Click event, this is correct behavior, since the Click event (which is inherited from the System.Windows.Forms.Control class) fires without regard to the area of the control that was clicked, and has no bearing on any item's active state.