Hello,

Thank you for the provided screenshots.

My suggestion in order to achieve different styling on the Items and descriptions is to use UltraDropDown instead of ValueList and set it to the Column ValueList Property:

 private void UltraGrid1_InitializeLayout(object sender, Infragistics.Win.UltraWinGrid.InitializeLayoutEventArgs e)
        {
            e.Layout.Bands[0].Columns[2].ValueList = this.ultraDropDown1;
        }

UltraDropdown is a much more powerful ValueList. It is essentially a dropdown UltraWinGrid (although it is limited to a single band). Just like the WinGrid, it must be bound and has a wide range of Appearances and features such as sorting, filtering, and resizable columns. You could change its appearance in order to look like a Value list.

I have created a small sample where the Items are on the even rows and the descriptions on the odd. So you could set the ForeData Bold property to true only if the row index is even and change the font size using the SizeInPoints property:

 private void UltraDropDown1_InitializeRow(object sender, Infragistics.Win.UltraWinGrid.InitializeRowEventArgs e)
        {
            if(e.Row.Index % 2 == 0)
            {
               e.Row.Appearance.FontData.Bold = Infragistics.Win.DefaultableBoolean.True;
            }
            else
            {
                 e.Row.Appearance.FontData.SizeInPoints = 7;               
            }
        }

I have attached a sample application, that uses this approach. Please test it on your side and let me know if I may be of any further assistance.

Sincerely,

Teodosia Hristodorova

Associate Software Developer

Using UltraDropDown is definitely the way to go here. But using every other row of data for Name and Description is not ideal. Your sample is handling MouseDown and diverting the selection to the appropriate row, but that won't work if you select a row in the dropdown via the keyboard. 

A better way to handle this is to use Groups and Levels. That way, you have a single dropdown row that has two levels of data in it. And you don't need to worry about where the user clicks.

I changed the sample to do it this way so that keyboard interaction still works correctly. I also made some minor changes to other areas - like I changed the Category column to an Integer so it matches up with the ValueMember of the DropDown. This was causing some internal exceptions and the dropdown had some weird display issues when you dropped it down in the original sample. :)