How could it be that?

[Aleksey Timonin]

Hi guys!
I suggest you to start session of questions to Microsoft Visual Studion
team. We have here MVPs comunity, that have influence in Microsoft world and
may help us to make the soft empire to resolve (in the end) basic Visual
Studio bugs. Let's help them and will list such a bugs in this session.
Let's make the world better
I suggest you start your question with "How could it be that..."

So here are problems I have find during my today work in Visual Studio 2008
on WinFoms project.

How could it be that:
1. ...button control has "Image" property and doesn't have mechanism to make
the image transparent? Amaizing that such ability has a ToolStrip buttons!
Shouldn't it be the same?
2. ...button control has "Image" property, but doesn't have property for
image in disable mode?
3. ...ListBox doesn't has method moving Item from current place to another?
It's very useful when you implement "Up" and "Down" buttons to order items
in list.
4. ...when I set ListBox.Dock property to be align left, its height visualy
several pixels less than height of the Panel aligned left standing close to
it?

Join me!

 

[Marc Gravell]

re 4: set IntegralHeight to False and it will do what you want

Note that this frum is not the place for crusades. If you have real
questions or feedback, then fine: ask away - but don't make it a
squabble. That doesn't help anybody, and makes life unpleasant.

re the rest of your points: none of these are really Visual Studio
issues - they are related to the controls library (which is not the same
thing).

Re the image issues, I suspect WPF can do this without much effort.

Re the list... just removove it and add it at the new index - not tricky...

Marc

 

[Aleksey Timonin]

Thank you for IntegralHeight.
My project is WinForms project, so the advice with WPF doesn't useful...
About control library... It doesn't helps me that it is controls library
issue... Delphi makes the work perfect on the same controls, so I think
Microsoft could too.
Re the list... thats exactly what I have done. But it is trick... IMHO it
should be standard component method

It isn't war. It's just way to make QA. I just thought that it should be
important for Microsoft to know about people having problems with thier
products, in case they realy want to care about the people. List of such a
bugs will help them to improve the products. Once again it is just IMHO.

Aleksey

 

[Marc Gravell]

It's just way to make QA. I just thought that it should be

important for Microsoft to know about people having problems with
thier products

Absolutely it is importany! And if you feel it is warranted, then
"Connect" might be an option:

http://connect.microsoft.com/VisualStudio/

It doesn't helps me that it is controls library
issue... Delphi makes the work perfect on the same controls, so I think
Microsoft could too.

Yes... I was simply trying to highlight that there are different teams
involevd here... this doesn't look like it is specific to Visual Studio,
but rather to the winform implementation. There is a difference.

Marc

 

[Aleksey Timonin]

Of course they _could_. However, any given framework is never going to be

all things to everyone...

I agree with you. But if each 5th programmer should implement such
functionality itself, it makes the issue a "base feature". Microsoft do it
for ToolStrip buttons, so I don't see a reason why here should be another
functionality...

... But it's also not hard to implement yourself.

Not hard at all!!!! But why dammit each programmer should implement it? It
is BASE FEATURE!!!!

The word "bug" make you to be angry on me? Take my appology... But bug could
be in design too... Don't you agree with me?

Best regards,
Aleksey