The way I found to work around this bad design is to play with the so-called ''inactive selection back/front color'' so that when you change the focus to another control, the grid ''seems'' to be unselected. Of course, clicking on the first row won't fire the onselectedrowchange event because it's actually already selected so you'll have to detect ...

Too bad, they made SelectedItem a read only property. In EVERY grid control in the world, you can choose not to select anything. Even the most basic native VS control.

I have the same problem: the grid holds a number of item I want the user to select but the UI also displays some items that ARE NOT in the grid. Every time I refresh the grid based on a not-in-the-grid item, I get the first grid item display instead of keeping the focus to the current one. So you have to use a global variable to bypass the ...

Found the solution but it's ULTRA COUNTER INTUITIVE: you need to cast the collection of  Xceed.Grid.Row selectedRows property output by a - most likeley - inherited class CellRow. Thus, answer is: (Xceed.Grid.CellRow)gridControl1.SelectedRows[0].Cells[<field name>].Value

In the SelectedRowsChanged event, how to get the value of a selected row's cell by column name   I'm expecting something like  gridControl1.SelectedRows[0].Cells[<field name>].value  but Cells collection doesn't exist in this context....   Thanks

I also found the following way:gridControl1.Columns[<column name>].FormatSpecifier = ''###-###-###'';

Create the group object at design time and then assign the property groupBy at runtime

A google search pointed me to the doc, in case you look for it, it's here: http://doc.xceedsoft.com/products/XceedGrid/sitemap.html

Why isn't there any documentation about this product? I mean, something that you can read in .pdf, .html

How to group by programmatically ? And more generally speaking, since where is the getting start documentation explaining how to do basic stuff like this?