Kevin
Thu Aug 02 06:33:01 CDT 2007
> 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" <nobody@eu.con> wrote in message
news:%23JRPkcE1HHA.3916@TK2MSFTNGP02.phx.gbl...
> Kevin Spencer wrote:
>
>> 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