MSDN useless

[DirtyHowi]

I've been searching for the full list of event sequences with a check box, everything says all there is is checkchanged event, which is not working due to the fact it goes through twice and screws up the form.

so, it should be something like
mouse over
mouse down
mouse click
checkchanged
mouse up
??? <-- this is the one i want to put code in but can't find....

used to be you could goto the MSDN and they would have information, not anymore, it's all preaching about how great everyone is, and the help is even more useless than before.

does a check box have a validating event?

[mendhak]

I doubt it, it's a checkbox and it is logically an input element which always has a value. True or false. Hence it's always valid. If you are attempting to get the user to 'agree' to some terms or services and forcing him to check the checkbox, then that's logic rather than validation, and you will need to enforce this either in your codebehind by explicitly checking it or using some javascript to check for it in the onSubmit.

[mendhak]

Surely MSDN cannot create pages answering every conceivable question that a developer would pose...

[Hack]

What checkbox are you using?

VB6
VB.NET
Something else

[DirtyHowi]

k first off, it's winforms, vb.net 2005 (for now bwahahahaha) and i did figure it out, but with the advent of .net there is actually a trinary checkbox ability, using the checkstate property there is more than one possible value, true, false and nondetermined (or indeterminate).

the biggest complaint is i used to be able to get SOMETHING out of the MSDN, and no i don't expect that every query will be covered, but for the love of pete, when i look up iCloneable i should get some sort of explanation beyond the 2 lines they give it and the implements system.icloneable for vb.net as an example.

for as bad as the MSDN used to be (and it was bad, i normally look there as information of last resort or when i just needed a brain kick to get me going) it's completely useless now, all prostelize no choir.

[Atheist]

The MSDN library is huge and full of information, I cant understand how anyone can call it useless.

[RobDog888]

I would have to agree and disagree.

I agree that lately with 2005 they seemed to have posted only limited information about a function or property etc. Gone are some of the examples showing how the function is used in trade for a sentence of generic definition only.

Perhaps they just havent gotten around to creating the examples yet for the majority of it but come on its bee 3 years or perhaps 4 if you count thebeta stages.

But I do disagree that msdn is useless. I have found it more ebenficial to have then to have not in all my searches. True it may be difficult to locate something sometimes but to find it is well worth the effort.

[techgnome]

Same here.... since 2005 I've actually found MSDN to be MORE informative than the old VB6 version. As for the IClonable example.... I dunno.... the pages that came up for me seemed pretty informative. Told me exactly what it was for, and what methods were available (all one of them). The reason there isn't more code in the example, is that it's up to YOU how it gets coded...

Also, MSDN is a living document, and is still in the process of being written and examples being created. Instead of b!tching about it, why not use that Feedback form? That's what it's for.

-tg

[mendhak]

I see what you mean now and I agree with my cronies here, I loathed having to go to msdn.*.* when VB6 was out, but with .NET, it's improved in leaps, bounds and explosions of celestial proportions. Even when examples aren't given, it isn't that hard to figure something out given some time. Or lots.

[RobDog888]

And when you cant figure it out you can just post the question in its relevalent forum and not have to worry about someone telling you to search msdn

[DirtyHowi]

i do that now when i really need to, (like the boss is saying i'm gonna break the desk with my skull). but it just seems that for something that should be mature technology it should be easier to find what i need is all.

i understand things change etc, otherwise i'd still be writing in vb3, and while i suppose iCloneable is not a good example, the life cycle of a button used to be there.