numericUpDown Control - double digits?
-
I am using a numericUpDown control which represents a minutes (for time) value. I want it to display 00, 01, 02, etc... for numbers less than 10. Is there a simple way to do this with a property (I reviewed the documentation, but didn't see anything immediately)? I know I could do it if I inherit the control, but I was hoping for a simple property or somethign to accomplish it. Something that I missed in the documentation. Can it be done without inheriting it?
There are only 10 types of people in this world....those that understand binary, and those that do not.
-
I am using a numericUpDown control which represents a minutes (for time) value. I want it to display 00, 01, 02, etc... for numbers less than 10. Is there a simple way to do this with a property (I reviewed the documentation, but didn't see anything immediately)? I know I could do it if I inherit the control, but I was hoping for a simple property or somethign to accomplish it. Something that I missed in the documentation. Can it be done without inheriting it?
There are only 10 types of people in this world....those that understand binary, and those that do not.
-
I am using a numericUpDown control which represents a minutes (for time) value. I want it to display 00, 01, 02, etc... for numbers less than 10. Is there a simple way to do this with a property (I reviewed the documentation, but didn't see anything immediately)? I know I could do it if I inherit the control, but I was hoping for a simple property or somethign to accomplish it. Something that I missed in the documentation. Can it be done without inheriting it?
There are only 10 types of people in this world....those that understand binary, and those that do not.
No property like this is available, but if you extend
NumericUpDownyou can simply overrideUpdateEditText. IfHexidecimalis set, be sure to call thebase.UpdateEditTextunless you want to handle this yourself. Also, when formatting the number, don't forget to take theThousandsSeparateinto account.Microsoft MVP, Visual C# My Articles
-
No property like this is available, but if you extend
NumericUpDownyou can simply overrideUpdateEditText. IfHexidecimalis set, be sure to call thebase.UpdateEditTextunless you want to handle this yourself. Also, when formatting the number, don't forget to take theThousandsSeparateinto account.Microsoft MVP, Visual C# My Articles
Thank Heath...that's kind of what I thought. I figured I'd have to inherit/extend it to make it work. I just wanted to make sure there wasn't a property for it that I missed before I went through all the trouble.
There are only 10 types of people in this world....those that understand binary, and those that do not.
-
Thank Heath...that's kind of what I thought. I figured I'd have to inherit/extend it to make it work. I just wanted to make sure there wasn't a property for it that I missed before I went through all the trouble.
There are only 10 types of people in this world....those that understand binary, and those that do not.
I take it that you looked at the class documentation for the
NumericUpDownclass, right? Deriving from your sig, "there are 10 types of people in this world...those that read the documentation and those that do not." :) (Unfortunately, most of the posters here fall in the latter category.) Typically, you can learn everything you need to know from the docs (add that to experience and reading articles on MSDN, CodeProject, et. al.). If some member overrides a base member of defined new and you find the documentation a little lacking on details, use ildasm.exe - the IL disassembler that comes with the .NET Framework SDK - to view the IL for the implementation in that assembly, or use a good decompiler like .NET Reflector[^] (though its decompiler rarely incorrect / incomplete). You can learn a heck of a lot that way - perhaps even pick up a few pointers from the developers at Microsoft who wrote the base class libraries.Microsoft MVP, Visual C# My Articles
-
I take it that you looked at the class documentation for the
NumericUpDownclass, right? Deriving from your sig, "there are 10 types of people in this world...those that read the documentation and those that do not." :) (Unfortunately, most of the posters here fall in the latter category.) Typically, you can learn everything you need to know from the docs (add that to experience and reading articles on MSDN, CodeProject, et. al.). If some member overrides a base member of defined new and you find the documentation a little lacking on details, use ildasm.exe - the IL disassembler that comes with the .NET Framework SDK - to view the IL for the implementation in that assembly, or use a good decompiler like .NET Reflector[^] (though its decompiler rarely incorrect / incomplete). You can learn a heck of a lot that way - perhaps even pick up a few pointers from the developers at Microsoft who wrote the base class libraries.Microsoft MVP, Visual C# My Articles
Yes, I did read the documentation, the problem is that Microsoft documentation isn't always as solid as it could be. Once you've "done it", then you see in retrospect how to "do it", but that doesn't mean the documentation just explains every nuance. Far from it usually. That was why I said up front that I knew it was possible if I inherited the class, but wanted to make sure there wasn't a proprety or something like that I was missing. I'll keep that in mind about the ildasm.exe....I remember you showing me that on the COM DLL problem I had last week.
There are only 10 types of people in this world....those that understand binary, and those that do not.