I use 8.1 and Vista and XP. In several columns I use UltraComboEditors as editorcontrols with 30'000 entries. The scrolling seems to stagnate when these columns come into view.

Manuel

UltraGridColumn col = mGrid.DisplayLayout.Bands[iBand].Columns[sCol];
UltraComboEditor ed = new UltraComboEditor();
EditorButton bt = new EditorButton();
ed.ButtonsRight.Add(bt);
ed.DropDownButtonDisplayStyle = Infragistics.Win.ButtonDisplayStyle.Never;
col.EditorControl = ed;
ed.DataSource = table;   // a DataTable with 30'000 entries
ed.DisplayMember = table.Columns[1].ColumnName;
ed.ValueMember = table.Columns[0].ColumnName;
ed.BindingContext = mGrid.BindingContext;
ed.DataBind();

 So each new editor in at least one column is bound to a DataTable with 30,000 rows?  Are these all bound to the same DataTable, including the grid?  One solution that might would would be to turn off the SyncWithCurrencyManager of the grid to see if that speeds up anything.  My guess as to what's happening is that when the grid needs to render the values in the columns with those large editors, it needs to look up the value in the list to pull out the appropriate DisplayMember and ValueMember, but I'm not entirely sure offhand.

-Matt

Turnig off SyncWithCurrencyManager did'nt help. 

The gird displays customer-adresses (30'000), each adress can have a special delivery- and billing-adress, and a reference to a main adress (i.e. always a self-reference to the same table with 30'000 rows).

To help the user choose the right adress, I diplay them in an UltraComboEditor. ValueMember is the internal ID of the customer, in the DisplayMember I show the customer-number with the customer name:

Data: ID is 1234, customer-number ist 100002, name ist 'My Customer'
Combobox: Value = 1234, Text = '100002 MyCustomer'

Maybee there is an other way to provide this functionality..

 Manuel

Hi Mike,

 Thanks for the hints. I've got the UltraCombo working, it is about 3 times faster.

Last points:

- Is there a way to hide the DropDown-Button (UltraComboEditor: DropDownButtonDisplayStyle = Infragistics.Win.ButtonDisplayStyle.Never)?

- It seems that the Click-event of the button is not fired:

UltraCombo ed = new UltraCombo();
EditorButton bt = new EditorButton();
ed.ButtonsRight.Add(bt);
bt.Click += new EditorButtonEventHandler(bt_Click);
col.EditorControl = ed;

Hi Manuel,

If you need an editor button, then no, you can't use UltraDropDown or a ValueList. But you can use UltraCombo (not UltraComboEditor). UltraCombo (which is in the WinGrid assembly) supports EditorButtons and all the normal features of a ValueList and it's also got binary search functionality. 

I'm not surprised this is a little slow. Every cell in the column with the UltraComboEditor has to search the list of 30,000 items every time it paints to find the matching item. It will cache the index of the item the first time it finds it, so it really only has to search once, but it's still quite a lot of linear searching. 

This will be especially problematic if the grid cell contains a value that does not exist on the list, since this means that the search has to search every item on the list and cannot cache the index so the entire search has to repeat every time. 

It's also possible that there are exceptions occurring during the search. This will happen sometimes if the data type of the grid column doesn't match up with the data type of the items in the list. Try setting the Visual Studio IDE to break on all run-time exceptions and see if any exceptions occur.

Whether exceptions occur or not, one thing I can recommend is that you do not use UltraComboEditor to provide your list. This is inefficient anyway, since the ComboEditor is a standalone control with an edit portion that is not being using by the grid. A ValueList would be a more efficient way to provide a simple dropdown list in the grid cell.

But an even better thing to use is the UltraDropDown control.This will not only alleviate the issue of an unused edit portion, the UltraDropDown also has a much more efficient way of searching the list - it uses a binary search by default. This means that there will be a slight performance hit the first time the dropdown is populated while it builds a sorted list of data, but it will be a lot more efficient during normal use.