By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,836 Members | 2,023 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,836 IT Pros & Developers. It's quick & easy.

Suggestion to abolish the "Click" event

P: n/a
Hy everyone, just wanted to share a thought regarding UI.
If you really think about it, events such as "Click", "DoubleClick",
"KeyDown", "KeyUp", etc... (which clutter every winforms control we see) are
mostly annoying and sometimes even harmful.
How does knowing a control was clicked by the mouse (and how many times it
was clicked) help a client object know what the user intended to do by that
How many times have you found yourselves handling mouse and keyboard events
the same way to cover up this design flaw?
How am I supposed to be content with an application which uses the
"DoubleClick" event in a million different places, when the next version of
Windows might set a new - "TripleClick" event - which will become standard
for activating items...
As a replacement I suggest the Winforms (and Webforms) team start coming up
with better designed controls which provide their client objects with a more
meaningful interface. For Example, a button with an "Activate" or "Execute"
or "Operate" event seems much more reasonable to me.

And while I'm on the subject of Winforms controls, I really don't see the
point in exposing so many attributes of controls, while not giving developers
any tools to centrelize control styles (I'm thinking... CSS) on an
application level. I found the ComponentResourceManager (which I guess was
intended mainly for internationalization) and I'm using that for now. But
still, there is a lot to be done here - and I, for one, think it's a lot more
important than new or better-styled controls.

Anyone with me on these subjects?
Nov 22 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.