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

The Reason why ComboBox control is unfinished (3 times !)

P: n/a
Hi !

I have a question : the ComboBox control have NO single border, and height
is at least 1 pixel higher than TextBox.

There is absolutely NO good reason for making a ComboBox looking that way.

My question is WHY Microsoft did that in the 3 versions of Visual
Studio/.NET releases (and probably will stay like that in the next version
of VS) ????

A) MS Developer forgot 3 times to finish that control ?
B) The same beginner did the same mistake 3 times and QC missed that 3
times ?
C) Microsoft want to be sure to keep design advantage on their customers
giving them unfinished controls ?
D) Microsoft encourage their customers to learn about control design
development ?
E) Other ?
I'll bet on the C.

If somebody have an idea.. I'm curious to know the explanation.if there is
any.

Steph.


Nov 22 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a

You sound really frustrated. What exactly are you trying to accomplish
that you are having trouble doing without the single border or pixel
height that matches a text box?

They probably didn't think that devoting resources to making it more
robust would be worth the amount of usage those extra features would
use.

-Aaron
TheSteph wrote:
Hi !

I have a question : the ComboBox control have NO single border, and height
is at least 1 pixel higher than TextBox.

There is absolutely NO good reason for making a ComboBox looking that way.

My question is WHY Microsoft did that in the 3 versions of Visual
Studio/.NET releases (and probably will stay like that in the next version
of VS) ????

A) MS Developer forgot 3 times to finish that control ?
B) The same beginner did the same mistake 3 times and QC missed that 3
times ?
C) Microsoft want to be sure to keep design advantage on their customers
giving them unfinished controls ?
D) Microsoft encourage their customers to learn about control design
development ?
E) Other ?
I'll bet on the C.

If somebody have an idea.. I'm curious to know the explanation.if there is
any.

Steph.
Nov 22 '06 #2

P: n/a
"TheSteph" <Th******@NoSpam.comwrote in message
news:eI**************@TK2MSFTNGP03.phx.gbl...
Hi !

I have a question : the ComboBox control have NO single border, and height
is at least 1 pixel higher than TextBox.

There is absolutely NO good reason for making a ComboBox looking that way.

My question is WHY Microsoft did that in the 3 versions of Visual
Studio/.NET releases (and probably will stay like that in the next version
of VS) ????

A) MS Developer forgot 3 times to finish that control ?
B) The same beginner did the same mistake 3 times and QC missed that 3
times ?
C) Microsoft want to be sure to keep design advantage on their customers
giving them unfinished controls ?
D) Microsoft encourage their customers to learn about control design
development ?
E) Other ?
I'll bet on the C.
Wrong bet. The .NET combobox is a thin wrapper around the good old Win32 Combobox - it
existed long before .NET and as such have nothing to do with .NET nor will it change with
the next version of VS.

Willy.

Nov 22 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.