I have an io field where I want to accept a number from 0 - 99,999. So I use the Ultra Numeric Editor and set the Min Value to 0, the Max Value to 99999. What's irritating me is when the field is displayed on the screen it has a Zero in it (which is correct) and when I tab into the field, the cursor is set in front of the 0. Consequently, if I enter a 1, the number becomes 10... I don't want that, I want it to change the value from 0 to 1. What can I set to have the Value automatically selected when I enter the field so that whatever I type OVERWRITES the value that was in there?
Why does the UltraMaskedEdit select the value when you tab into the field but the UltraNumericEditor doesn't? I would use the UltraMaskedEdit control as my Numeric IO field if I could set it to right justify the value and enter the value from the right side like a Numeric editor would, but unfortunately, I can't seem to make it do that... More irritation...
My second complaint on the Numeric Editor is that if I delete the 0 then try to exit the field, I get a beep and the cursor won't leave the field until I put in a 0 or some other value. (I realize I DO have the Nullable property set to False, which is what I want) How can I set a Default (like 0) value for the field?
Finally, I STILL don't get emailed replies to my posts, even tho I ask it to.
Mike Saltzman"] ... it seems to me that the event doesn't fire because it's essentially useless on a button. Why would you ever want to use a DoubleClick event on a Button tool?
... it seems to me that the event doesn't fire because it's essentially useless on a button. Why would you ever want to use a DoubleClick event on a Button tool?
That same argument could be used for ANY control that utilizes both the Click and DoubleClick events. In Windows Explorer I can slowly click twice on a file name to rename it, or I can doubleclick it to open it. In a grid control I can click once on a row to "select" it, or I can doubleclick on it and perform some other function. There are many cases (controls) where a single click performs one action while a doubleclick performs a different action... and it's quite convenient and usefull. I could argue that it's "not intuitive" but, that's really beside the point. It obviously works quite well.
More specifically, in my particular case, I have a button that opens an explorer bar with various options that can be performed on a particular file (SQL Table). I want to have the SAME button just automatically start up option 1 (the main editing program for that particular file in this case) on the DoubleClick event. Again, whether that seems "intuitive" or not doesn't really matter. The users will quickly learn how it works and they will appreciate that they don't have to click once to open the menu bar, and then click again to edit the file.
I agree that it might not be the most obvious or intuitive thing. And if it's not documented, then it certainly should be.
Steve Smith said:PS - None of the RSS links in the forum appear to work. :(
I tried it out and they don't work for me, either. I will notify the forum folks so they can fix it.
I'm not saying I disagree with you about a user double clicking button. My only point was that if we have a control where all the menu object events are handled by the parent toolbar manager, as a developer using the control my first assumption would be that the events listed are going to work for all tool objects and not just some here and some there. I guess you would call that "object normalization". It's kind of like having an unnormalized table where certain columns are valid or not depending on the data in the row. I'm not saying it's a bad design, it's just not necessarily developer intuitive at first glance until you figure out what the thought process was behind it.
But I know... it's not your area.
PS - None of the RSS links in the forum appear to work. :(
Steve Smith said:I don't know for sure since I haven't looked, but I doubt there is documentation that says oh by the way you can't use the tool double click event for X,Y and Z tool controls. I have to agree that since the event is fired on the toolbar manager which is global to all the tool objects that they all should handle the event. Just my two cents.
As I said, this forum is really not the right place to discuss this and the toolbar isn't really my area. But it seems to me that the event doesn't fire because it's essentially useless on a button.
Why would you ever want to use a DoubleClick event on a Button tool? I know of no application that does this. It would not be intuitive to a user that he needs to double-click a button instead of just clicking on it once. How would the user know? Wouldn't they be confused when then click on the button and nothing happens?
You really can't use both Click and DoubleClick on the same button, because Double-Click doesn't replace Click - you would get two click events in addition to every double click.
Wolven said:Personally, I absolutely despise Null. It's just a pain in the butt. Except in extremely rare cases, (and NONE in accounting or any other business application I've ever written) it serves no purpose other than creating a whole lotta program errors and stupid test statements to insure that a value isn't null.
Well, you can't blame Infragistics for that. Null is a feature of the programming language, and it's useful in many applications where you want to distinguish between an actual value and the absence of a value.
Wolven said:All that said, If Infragistics just can't bring themselves to agree that an emptly NON NULLABLE Numeric field should automatically default to 0, then AT LEAST give us the ability to set a Default Value, (which would be zero 99% of the time).
Feel free to Submit a feature request to Infragistics.