Hi,

It occurs with different sort of components which take focus:

If I use a ultraNumericEditor to edit in my cell it works (Grid lostFocus is correctly sent), but if I use default behavior to edit in cell or a ultraTextEditor it does not works (Grid lostFocus is not sent when another component take the focus).

Anne-Lise

The Leave event of the ultragrid also never gets thrown.

Tanner Stevenson said:

The Leave event of the ultragrid also never gets thrown.

Well.. the Leave event will not fire unless focus leaves the grid. This will not happen in this case because you are clicking on a toolbar button and the toolbar button does not take focus. It would fire if you clicked on a regular button or some other control that takes focus. 

Tanner Stevenson said:

Or how I could commit character literals to my data objects?

I still do not understand what you are asking. What is a "character literal?" The grid stores whatever the Value property of the cell is. 

Mike Saltzman said:

Well.. the Leave event will not fire unless focus leaves the grid. This will not happen in this case because you are clicking on a toolbar button and the toolbar button does not take focus. It would fire if you clicked on a regular button or some other control that takes focus. 

I've already told you that the button does take focus, or else I wouldn't see the Leave event be thrown when I have an UltraFormattedTextEditor in the cell, so that explanation does not apply. Also I'm still confused as to why any of the events of an UltraTextEditor do not get thrown such as Before/AfterEnterEditMode or GotFocus. And above all, why would the behavior of the grid be different based on the editor component in the selected cell? Shouldn't the grid be agnostic to the editor component? This is seriously one of the most frustrating aspects of this grid. The functionality details are so swept under the rug, no one seems to know why the table behaves in the way it does. 

Mike Saltzman said:

I still do not understand what you are asking. What is a "character literal?" The grid stores whatever the Value property of the cell is.

What I mean is if I type '&', I want that character to be saved in my data source instead of '&'. I have figured out a hack way to do this, so this discussion is now probably moot. Using an UltraFormattedTextEditor I subscribed to the BeforeCellUpdate and did the following if anyone else has a similar issue:

if (e.Cell.Column.DataType == typeof(string))
{
   var columnProperty = e.Cell.Row.ListObject.GetType().GetProperty(e.Cell.Column.Key);

   if (columnProperty != null)
   {
      columnProperty.SetValue(e.Cell.Row.ListObject, e.Cell.Text);
      e.Cancel = true;
   }
}

Thanks for trying.

Tanner Stevenson said:

I've already told you that the button does take focus, or else I wouldn't see the Leave event be thrown when I have an UltraFormattedTextEditor in the cell, so that explanation does not apply.

So you are saying that the Leave event of the grid fires when you are in an UltraFormattedTextEditor cell and click on the toobar button, but not when you are in a regular text cell? I have no explanation for that behavior. That's not the way it works. If you button takes focus, then the Leave event of the grid should fire. If it's a Toolbar button or some other button that doesn't take focus, then the event will not fire. The leave event is part of the DotNet framework, it's not something specific to the grid. But if that's the behavior you are getting and you can reproduce that in a small sample project, I would be happy to take a look and see what's going on. 

Tanner Stevenson said:

Also I'm still confused as to why any of the events of an UltraTextEditor do not get thrown such as Before/AfterEnterEditMode or GotFocus.

The events I am referring to here like Leave are events on the grid, not the editor control. If you assign an UltraTextEditor control or UltraFormattedTextEditor as the EditorComponent of a grid column, then the grid does not use that control. The control simply provides a copy of it's internal editor to the grid. So you cannot use any events on those controls (with a few rare exceptions like EditorButton events). 

Tanner Stevenson said:

And above all, why would the behavior of the grid be different based on the editor component in the selected cell? Shouldn't the grid be agnostic to the editor component? This is seriously one of the most frustrating aspects of this grid. The functionality details are so swept under the rug, no one seems to know why the table behaves in the way it does. 

It depends what behavior you are talking about. For the most part, in most of the applications that use the grid, it's irrelevant to you, the developer, what control (or no control) is being used for editing a cell. The implementation details of the grid are not generally important. I'm still not really sure why this is giving you so much trouble, and like I said, the behavior you are describing is not something I've ever heard of before. 

Tanner Stevenson said:

What I mean is if I type '&', I want that character to be saved in my data source instead of '&'. I have figured out a hack way to do this, so this discussion is now probably moot.

Ah, I see. That would not work. FormattedText is xml-based and it has to use escape codes for certain characters to support formatting. If you stripped out the formatting, you would lose it the next time you ran the application. If you are not actually using any formatting and just want raw text but are using FormattedTextEditor for some other reason, then one thing you might do it hide the "real" column and add an unbound column to your grid that shows the FormattedTextEditor to the user. Then you have to handle translating between the two.

Hi Mike,

I have a small sample project to demonstrate this functionality discrepancy. How would you like me to share it with you?

In the project, you can switch which editor component is being put in the cells through the CustomGrid class. I realized that the Leave event doesn't get thrown with either editor, but the grid's lost focus event does get thrown with the UltraFormattedTextEditor. So by handling that event, I can save my edits to the data source before the button's command is executed. I have also added a handler for the toolbar button's GotFocus event (in PageView.xaml.cs) so you can verify for yourself that the button does in fact gain focus.

I think that's correct, yes. It would certainly explain all of the behaviors you are getting. 

Okay so the real confusion then is the word "focus" and even though a form of "focus" is placed on the button, it is not the type that is necessary to throw the Leave event. Would you agree?

Well, thank you for your time and help.

Hi Tanner, 

My guess is (and I say guess because we're really talking about the DotNet Framework here and not the Infragistics controls any more) that since the Toolbar is a separate windows and the GotFocus and LostFocus are tied to windows messages that as far as Windows is concerned, the toolbar gets focus. But that's not the same kind of focus we're talking about when we talk about focus in DotNet. Which is why, once again, Microsoft's documentation recommends using Leave and Enter and not using GotFocus and LostFocus.

If the toolbar button does not gain focus, why then is the GotFocus event thrown when the toolbar button is clicked?

Hi Tanner, 

Tanner Stevenson said:

I realized that the Leave event doesn't get thrown with either editor, but the grid's lost focus event does get thrown with the UltraFormattedTextEditor.

Okay... well, that makes perfect sense and it's one of the main reasons why using the LostFocus event is NOT a good idea. LostFocus is tied to the Windows messages. When a grid cell with a FormattedTextEditor is in edit mode, the grid has focus. Therefore, when you click on some other control, the grid loses focus. 

But, if the grid does not have focus, because it contains a child control (like a TextBox) which is what happens when a regular text cell has focus, the event will not fire. It doesn't fire because the grid didn't lose focus, because the grid didn't HAVE focus. The TextBox did. 

If you really want to jump through these kinds of hoops to make this work, then you could handle the grid's ControlAdded event and hook the LostFocus event of the child controls that are added to the grid. You would, of course, also want to unhook the event in ControlRemoved. But this isn't going to work very well for that you want, either, because the TextBox will lose focus when you leave one grid cell and move to another one, for example. In such a case, the TextBox loses focus and the grid gets focus. 

This complexity with child control is why it's not a good idea to rely on GotFocus and LostFocus in DotNet for WinForms. The Enter and Leave events take care of all the child controls for you so you don't have to worry about it. Of course, they only fire when another control actually takes focus, and as we've already covered, the Toolbar buttons don't. 

So after all this, we are basically back where we started. The simplest and easiest way for you to solve this problem is to simply call UpdateData on the grid in the click event of your toolbar button.