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.
Hey Mike, for some reason I can't get any response to this question in the Toolbar section of the Forum... so I'll ask it here.
I'm TRYING to utilize both the ToolClick and the ToolDoubleClick events using an UltraToolBarsManager Toolbar, but the ToolDoubleClick event never happens. Why? Obviously the ToolClick event is intercepting it before the ToolDoubleClick can be fired... but that SHOULDN'T be the case.
Mike said: No, 0 and null are not the same thing.
No, 0 and null are not the same thing.
Apparently you missed the part about the control being set to NOT NULLABLE. If it's a NOT NULLABLE Numeric control or Input Mask and no value is entered then... Wouldn't it make REALLY GOOD LOGICAL sense that the value SHOULD be set to 0 (zero) automatically??? :)
Wolven said: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'm not sure what you mean by "Every other Windows input field control", but as I said above, I tried this same test with the inbox TextBox control and it behaves the same way. It remembers the SelectionStart and SelectionLength that it had the last time it has focus and when you tab into it, it returns to the same state.
Wolven said: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.
I don't think this has anything to do with tabbing into the control. It just determines how SelectAll works.
Wolven said: 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???
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???
LOL... Hey, don't knock 'em if you've never worked with one... :)
Inspite of what you might think, the S\36 was in many areas WAY, WAY, WAY more advanced than any PC when it came to multi user business applications, Security (NEVER heard of one getting a "virus", EASE OF USE, and EASE OF PROGRAMMING. The fact that a great many larger businesses still run on AS\400's is not because they are ignorant, or stupid.
While I do appreciate the GUI capabilities of PC's, they are not nearly as sophisticated as the AS\400 (I Series, or whatever they call it now) when it comes to having a fully integrated and STABLE Operating System, Database, Security and Programming environment. While the PC's are sloooowly getting there, it amazes (and irritates) me that they can be less sophisticated than machines that were designed DECADES ago and had less than 1\10 the processing power and memory.
Hey Wolven,
I don't know if you saw, but they created a support incident for this issue. I think it would be safe to assume that we'll have to wait for the next release before it is addressed.
PS - You can't say you programmed on a system 36 without hinting at your age. I've seen a system 36 once in my life if that tells you anything. I hear they make great space heaters.