ReadOnly property according to M$

[Marius Horak]

Set NumericUpDown ReadOnly property to true.
Click the Up or Down arrow and watch.
Well, so ReadOnly applies to keyboard only.
Wrong, press Up or Down keys and watch.

I WANT MY MONEY BACK!!!

MH

 

[Kevin Spencer]

From the .Net SDK:

Gets or sets a value indicating whether the text can be changed by the use
of the up or down buttons only.(inherited from UpDownBase)

--
HTH,

Kevin Spencer
Microsoft MVP

Printing Components, Email Components,
FTP Client Classes, Enhanced Data Controls, much more.
DSI PrintManager, Miradyne Component Libraries:
http://www.miradyne.net

 

[Marius Horak]

Gets or sets a value indicating whether the text can be changed by
the use of the up or down buttons only.(inherited from UpDownBase)

So what?
If you buy a car you expect that pressing the brake pedal will slow
down the car. Always, not only when you are driving downhill. Do you
always read instruction for something that should be obvious? In case
of DotNet one needs a year to read all documentation before starting
writing the first line.

What I ment was that M$ is not consistent in its approach to properties
and their functions. And after such experience, one may expect that the
Enabled property may work in different way with different controls.

MH

 

[Mr. Arnold]

What I ment was that M$ is not consistent in its approach to properties
and their functions. And after such experience, one may expect that the
Enabled property may work in different way with different controls.

There is nothing you can do about it other than not use the product. So why
piss and moan about it in the NG?

 

[Norman Yuan]

More technical thought:

NumericUpDown control is "derived" from TextBox, I guess, hence the readOnly
property means whether you can enter numeric value directly or not. Think
further, it make sense to me that ReadOnly in this case only means you
cannot enter numeric value into the textbbox. However, the up/down arrows
should be able to change the value when it is "ReadOnly". If you do not want
the value to be changed in anyway, you would set "Enabled" to False. or if
you do not need its value being changed, you can simply use TextBox (with
ReadOnly set to True) instead, without the useless up/down arrows sitting
besides.

Or it simple a bit tricky issue, but I would'nt want my money back and quit
on programming Windows altogether, just because of this minor issue.
Otherwise, there is simply too many things to stop anyone doing programming
at all.

 

[Marius Horak]

There is nothing you can do about it other than not use the product.
So why piss and moan about it in the NG?

It makes me feel better, at least for a moment.
On other hand, most of the progress was made by people who were pissed
off with tools they had to use.

MH

 

[Mr. Arnold]

It makes me feel better, at least for a moment.
On other hand, most of the progress was made by people who were pissed
off with tools they had to use.

I suggest that you piss in the right direction to the vendor, because
nothing is going to happen in the NG for you.

 

[Kevin Spencer]

So what?

If you buy a car you expect that pressing the brake pedal will slow
down the car. Always, not only when you are driving downhill. Do you
always read instruction for something that should be obvious? In case
of DotNet one needs a year to read all documentation before starting
writing the first line.

A software Control is not a car, and in fact, has almost nothing in common
with a car. The analogy does not hold.

A good programmer is not surprised when a component developed by another
party does not behave according to his or her initial assumptions. "Obvious"
is a subjective term, as well as the evaluation "should be," based upon
one's own perception and experience of life. At any rate, a good programmer,
when faced with an unexpected result, makes an investigation as to the
cause, which is what I did, by reading the SDK documentation. It took me
less than 5 minutes.

As for needing a year to read all the documentation, I have been reading it
for over 5 years, and read it several hours every day, with no end in sight.
There are literally thousands of classes, not to mention technologies and
architecture in there. Your expectations with regards to needing to read the
documentation are unrealistic. The amount of documentation is proportional
to the amount of software being documented.

As for your criticism of "M$," I suggest you try Java. The grass only seems
greener on the other side of the fence when one has not tasted it.

--
HTH,

Kevin Spencer
Microsoft MVP

Printing Components, Email Components,
FTP Client Classes, Enhanced Data Controls, much more.
DSI PrintManager, Miradyne Component Libraries:
http://www.miradyne.net

 

[Marius Horak]

I suggest that you piss in the right direction to the vendor, because
nothing is going to happen in the NG for you.

Do you mean microsoft.public.dotnet.framework.windowsforms does not
belong to Microsoft? Did I miss Microsft takeover by Zorland?

MH

 

[Marius Horak]

A software Control is not a car, and in fact, has almost nothing in
common with a car. The analogy does not hold.

Blast, my system for a car rental company is now worth nothing. I have
there CarControl user control and CarClass class.

At any rate, a good programmer, when faced with
an unexpected result, makes an investigation as to the cause, which
is what I did, by reading the SDK documentation. It took me less than
5 minutes.

Well, it took me less than 20 seconds to discover that ReadOnly applies
to the text and not to the buttons and that a workaround would be
Enabled.

As for needing a year to read all the documentation, I have been
reading it for over 5 years, and read it several hours every day,
with no end in sight.

I spend this time drinking bubbles. It's more enjoyable.
And funny thing, everytime I changed job (13 times) my income was
higher. Now I can afford to work for pure pleasure and to wind up
Arnold.

As for your criticism of "M$," I suggest you try Java.

Been there. Another crap language. I my life as a programmer I used 21
languages + HTML crap, writing for PCs, minis and mainframes. Only
NATURAL (mainframe) and C# are any good. So I stick to C# until someone
discovers that one mainframe is better than a network of PCs.

http://tinyurl.com/33ce28

MH

 

[Mr. Arnold]

Do you mean microsoft.public.dotnet.framework.windowsforms does not
belong to Microsoft? Did I miss Microsft takeover by Zorland?

What? Come on man can you act like you have some kind of sense?

Do you think that anyone here as control of the product? Post to MS to the
vendor of the solution. There is a whole problem resolution department for
the MS productions where you can report a bug or discuss change for a
product, find it.

Maybe, this is beyond your comprehension on how to do things. Or are you
trolling me, which I wouldn't put it past someone like you that needs to
whine and b*tch.