Hey Mike,

I found the same issue as you describe with the Ultra Masked Edit control.  i.e. It selects all the data the first time you enter the field but if you type something and move away, when you re-enter the field it doesn't select the data.  My question is, Why not?  Every other Windows input field control I've used does (as far as I know).  I think it SHOULD select all the data each time you enter the field whether the data has been changed or not. 

I did notice that the Ultra Numeric and Masked Edit controls have a property called; SelectAllBehavior.  I tried setting it to the two different settings but didn't really notice any difference.  I did find that two Masked Edit controls that APPEAR to have all the properties set identically; mainly Edit As "String" and Input Mask "C" and SelectAllBehavior "SelectEnteredCharacters", behave differently.   On one of them, it behaves just the the numeric fields we're discussing.  The other one selects the data even after you change it, move away and then tab back in.  I haven't been able to find what's making the difference.

Regarding the Default Value...  If it's a Numeric Editor, and it's set to Not Nullable, and there isn't any data in the field, Wouldn't it make sense that the value SHOULD be set to 0 (zero) automatically??? 

And if it's a Masked Edit control with a Numeric Input Mask and it's set to Not Nullable, and there isn't any data in the field, Wouldn't it make sense that the value SHOULD be set to 0 (zero) automatically???  

It certainly seems to me like it should.   :)

As for my emails...  I get the "noreply" emails from the support people when they email me regarding open cases.  But I don't get emails when people reply to my posts for some odd reason. 

Wolven said:

A:   It WOULD work if your controls were "smart" enough to not fire a Click event twice along with the DoubleClick event.  (yeah, yeah, yeah, I know... that's how the infinitely wise MS does it)

This is not something that Infragistics invented. It's not even specific to DotNet - it's simply the way Windows works. When you click on something, the machine does not have any way of knowing that you intend to click a second time. It cannot see the future. So each click sends a click message.

I suppose Windows could simply buffer every click and not process it until the double-click time expired before deciding if a click is meant to be a single click or a double-click. But it seems to me this would make for a sluggish and annoying user experience.

Wolven said:

B:  The unlikely "breaking" scenario you gave would be due to some awfully sloppy programming on somebodies part.  I'd suggest that that type of programming deserves to get broken.

I don't think it's unreasonble for a developer to assume that since an event only fires for certain tools that it will continue to do so in the future.

Wolven said:

C:  I can't tell you how nice it is to have my tool suppliers KNOW what's best for me and my applications.  I wonder if that's how it works in every other industry...  Do the tool makers tell Ford that there's no compelling case to build a vehicle the way Ford wants to do it?  Do the subcomponent suppliers tell Boeing that there's no good reason they can see to build the part according to Boeings specs? 

I think we here at Infragistics are very open to customer requests and new ideas. But there are certain limits and standards that the operating system and the environment enforce upon us as well as our customers and there are good reasons for that.It provides consistency across applications and development tools.

Wolven said:

D:  While I can appreciate and understand that this particular "feature request" may not rank up at the top of your importance list ...  I don't appreciate being told that just because you don't see a need for it, there's no reason to do it.  Just because that's not the way it's always been done, isn't a good reason for not trying something new.  Innovation usually involves doing things a bit differently.

The fact that "that's not the way it's always been done" is irrelevant and I don't believe I made that suggestion.

My point here is that even if we did what you asked for and started firing the DoubleClick event for button tools, it won't help you acheive what you want here. So what would be the point?

Are you saying that we should add this feature simply because it was requested by a single customer - even though there is no practical use for it and it will take time away from the development of other, more useful, features?

Or are you suggesting that in spite of the fact that Windows fires 2 click events along with a DoubleClick that the toolbars manager should not do so? In order for that to happen, the toolbar would either have to somehow know that a second click is coming, or else delay the processing of the click event until the DoubleClick time (which is a system setting and can be changed) expired. Which means clicking on buttons would be slow an unresponsive.

Wolven said:

E:  Finally, I've thought about this "we can't change the broken behaviour because it might break someones application" problem I keep running into.  It seems perfectly reasonable that when you come out with a new version (Like the upcoming Netadvantage 2009 vol 2), you could implement "breaking" style FIXES and changes as long as they were well documented in a "Breaking Changes" document.  This would eliminate the never ending reason for not fixing broken code. 

I agree. And we occassionally do this when it's neccessary.

Yehaw,  we agree on one outta five...  :) 

On the one we agree on, can we add a case to fix the broken behavior of the dropdown control I documented a while back?  SInce it could theoretically be a "breaking" change (even you agreed it wasn't very likely to cause a problem), you weren't willing to add it back when we were discussing it.  But if we could add it as a Breaking Change Fix for 2009 vol 2, that would be nice.

To what dropdown issue are you referring?

I answer about 20+ posts a day, so I don't remember.

MIKEY!!!  Where are ya?

Private Sub Application_Startup(ByVal sender As Object, ByVal e As System.Windows.StartupEventArgs) Handles Me.Startup

        Debug.Print(Thread.CurrentThread.CurrentCulture.ToString)

        'Thread.CurrentThread.CurrentUICulture = New CultureInfo("en-GB")

        '// Access any class from the Lipstick style pack assembly to

        '    // ensure that the assembly has been loaded. The assembly

        '    // automatically registers any themes that it contains

        '    // when it is loaded. Once this is done you can set the 'Theme'

        '    // property of the XamDataGrid, XamDataCarousel or XamDataPresenter

        '    // to one of its registered themes, in this case "Lipstick".

        '    //

        '    // Note: this would normally be done once in the App.xaml.cs file.

        Dim rd As ResourceDictionary = Infragistics.Windows.Themes.Lipstick.DataPresenter.Instance

        'Make textboxes auto select text on focus application-wide.

        EventManager.RegisterClassHandler(GetType(TextBox), _

                                          TextBox.GotFocusEvent, _

                                          New RoutedEventHandler(AddressOf TextBox_GotFocus))

        'and other controls as required.

        EventManager.RegisterClassHandler(GetType(Infragistics.Windows.Editors.XamMaskedEditor), _

                                         Infragistics.Windows.Editors.XamMaskedEditor.GotFocusEvent, _

                                            New RoutedEventHandler(AddressOf XamMaskedEditor_EditModeStartingEvent))

        EventManager.RegisterClassHandler(GetType(Infragistics.Windows.Editors.XamNumericEditor), _

                                         Infragistics.Windows.Editors.XamNumericEditor.EditModeStartingEvent, _

                                            New RoutedEventHandler(AddressOf XamNumericEditor_EditModeStartingEvent))

        EventManager.RegisterClassHandler(GetType(Infragistics.Windows.Editors.XamDateTimeEditor), _

                                        Infragistics.Windows.Editors.XamDateTimeEditor.EditModeStartingEvent, _

                                           New RoutedEventHandler(AddressOf XamDateTimeEditor_EditModeStartingEvent))

        Try

            'make sure user settings folder exists

            System.IO.Directory.CreateDirectory(MyGlobals.UserDataPath)

        Catch ex As Exception

        End Try

    End Sub

    ''' <summary>

    ''' When any textbox gets focus in app, select all text automatically.

    ''' </summary>

    ''' <param name="sender"></param>

    ''' <param name="e"></param>

    ''' <remarks></remarks>

    Private Sub TextBox_GotFocus(ByVal sender As Object, ByVal e As RoutedEventArgs)

        Dim tb As TextBox = CType(sender, TextBox)

        tb.Focus()

        tb.SelectAll()

    End Sub

    Private Sub XamMaskedEditor_EditModeStartingEvent(ByVal sender As Object, ByVal e As RoutedEventArgs)

        Dim tb As Infragistics.Windows.Editors.XamMaskedEditor = CType(sender, Infragistics.Windows.Editors.XamMaskedEditor)

        Try

            tb.SelectAll()

        Catch ex As Exception

        End Try

    End Sub

    Private Sub XamNumericEditor_EditModeStartingEvent(ByVal sender As Object, ByVal e As RoutedEventArgs)

        Dim tb As Infragistics.Windows.Editors.XamNumericEditor = CType(sender, Infragistics.Windows.Editors.XamNumericEditor)

        Try

            tb.SelectAll()

        Catch ex As Exception

        End Try

    End Sub

    Private Sub XamDateTimeEditor_EditModeStartingEvent(ByVal sender As Object, ByVal e As RoutedEventArgs)

        Dim tb As Infragistics.Windows.Editors.XamDateTimeEditor = CType(sender, Infragistics.Windows.Editors.XamDateTimeEditor)

        Try

            tb.SelectAll()

        Catch ex As Exception

        End Try

    End Sub