Not making a difference. Strange.

I put the call last in all the grid settings calls. Even in my little test app its not preventing ctrl+space from making the first cell white.

Fully written out, I have done this:

ultraGrid.DisplayLayout.Override.SelectTypeCell = Infragistics.Win.UltraWindGrid.SelectType.None;

Is that correct? Are there any other settings that may conflict with this one? (although, as I said, it is the very last one).

Correction:

grid.DisplayLayout.Override.ActiveAppearancesEnabled = DefaultableBoolean.False;

(Just in case someone else also needs this solution. Mike forgot the Override)

Hi Boris, thank you for enquiring. I tried all of Mike's suggestions.

Setting grid.DisplayLayout.ActiveAppearancesEnabled to False did the trick.

Mike's answer had a bunch of ideas, it seemed unhelpful to set "Verify Answer" to ALL of them :)

But I'll do that now, to close the thread.

Hello,

I wanted to know if you were able to solve your issue based on these suggestions or you still need help. Please let me know.

Hi,

kennethknoepfli said:

I just need to know how it is done correctly, in keeping with the philosophy of the UltraWinGrid.

I'm afraid it's not that simple. Without know why the cell is turning white, there's no way to tell you for certain how to turn it off. There are a wide variety of reasons why this might be happening. It could be selection, it could be the active cell, it could be coming from the code, it could be coming from the isl file. There's no way to know for sure without seeing it in action, or experimenting a but.

If you are loading an isl file, try commenting that out and see if it changes anything. You already tried turning off cell selection, so maybe try setting grid.DisplayLayout.ActiveAppearancesEnabled to False and see if that makes a difference. You could also try SelectedAppearancesEnabled.

These are not solutions, of course, I'm just trying to narrow down where the color is coming from.

If you could post a sample project demonstrating the issue, I could tell you for sure. But I understand how creating a sample of something like this could be problematic since you don't know what's causing it. What I sometimes do in a case like this is I take my real application and I start removing things until the problem goes away - just to narrow it down.

Ugh.

The production code already is full of extremely complex handling of Before/AfterActivated, MouseDown and semaphores to keep track of states on the Row level already.

I am not keen on introducing similar code on Cell level if a simple single-line initialization will do.

I just need to know how it is done correctly, in keeping with the philosophy of the UltraWinGrid.