Rumen,

I tracked on that earlier.  For some reason the control ignores the 'DisabledStyle' settings.  I am currently using 2007v3.  The way the control seems to be functioning is that the highlight changes as my cursor hovers over the item.  When my cursor hovers over a menu item that has it's enabled property set to False that menu item is not 'Highlighted' and cannot be selected.  That is a visual cue, but I think it may be confusing to new customers.

Maybe Preset I chose is interfering with it.  It seems to have made two styles, but never seems to have used them.  This menu is set to be a Popup menu.

We are using Infragistics 3.5 v8.3 of the UltraWebMenu and having problems with setting the DisabledStyle in C# and having the UltraWebMenu render the disabled items.

We created a wrapper C# library component for the UltraWebMenu and then set the items to be enabled / disabled in javascript or the CodeBehind of a page.

C# CODE

Infragistics.WebUI.UltraWebNavigator.UltraWebMenu ultraWebMenu = new Infragistics.WebUI.UltraWebNavigator.UltraWebMenu();

ultraWebMenu.ID = this.ID + "UltraWebMenu";

ultraWebMenu.CssClass = "WebMenu-DefaultStyle";

ultraWebMenu.WebMenuTarget = Infragistics.WebUI.UltraWebNavigator.WebMenuTarget.PopupMenu;

ultraWebMenu.DisabledStyle.CssClass = "WebMenu-DisabledStyle";

When the page finishes loading, the disabled items have no CSS.  Using JavaScript, we can alert the DisabledStyle property of the Menu's JS object; the alert is an empty box.  If we explicitly set the DisabledStyle in JavaScript, the disabled items of the menu appear properly.

JAVASCRIPT CODE

alert('the Disabled Class is: ' + objActionMenu.DisabledClass);

objActionMenu.DisabledClass = 'WebMenu-DisabledStyle';

alert('the Disabled Class NOW is: ' + objActionMenu.DisabledClass);

 Has anyone reported problems with the DisabledStyle.CssClass property of the C# object not being properly passed into JavaScript?  Or are we setting the DisabledStyle incorrectly?

Then maybe you can also try to explicitly set a different style for the Item that is being disabled, directly on its style - for example:

<ignav:Item Text="Top Item">
                <Items>
                    <ignav:Item Text="Sub Menu Item">
                    </ignav:Item>
                    <ignav:Item Enabled="False" Text="Sub Menu Item">
                        <Styles ForeColor="#666633">
                        </Styles>
                    </ignav:Item>
                    <ignav:Item Text="Sub Menu Item">
                    </ignav:Item>
                </Items>
            </ignav:Item>

or directly using

UltraWebMenu1.Items[0].Items[0].Enabled = false;
UltraWebMenu1.Items[0].Items[0].Styles.ForeColor = Color.Gray; 

It is hard to tell what interferes with styles. UltraWebMenu renders as standard <table> <tr> <td> and if you have global CSS style settings for tables or table cells, they will be propagated to the menu cells as well. In this case the only way to go would be to redefine explicitly the styles inherited from global settings in CSS, so that they are applied only for menu items (for example if you are using Default theme, that would be)

.igmn_Item
{
    background-color:Transparent;
    border:solid 1px Transparent;
}


.igmn_Disabled
{
    font-size:xx-small;
    font-family: Verdana;
    color: gray !important!;

}

You can add your own styles there and mark them as !important (a CSS clause making sure this specific rule will stick to the item and not an inherited/cascading rule)