« BBOP: the ubiquitous yet under-examined UI model | Main | Avoiding unnecessary questions in command UI »

October 24, 2005


Robert W. Anderson

Is this behavior new?

AutoScaleMode (plus some other features) replace the old AutoScale which defaulted to true. AutoScale has been deprecated. The new property, AutoScaleMode, is an enumeration. For Forms, it defaults to "Font".

It appears to me that this default behavior should be the same as what was in .NET 1.1.

One of the problems with auto-scaling is that the developer tends to assume that if it looks good on their machine, it will look good everywhere. In this modern day, we all expect VS2003/5 to handle this for us. But I am surprised still at how many times I try out new software only to find that I can add see the bottom of a dialog box (or a splash screen is larger than the bitmap inside of it). My main computer is a laptop with 1920 by 1200 LCD that I run at 120DPI resolution.

Perhaps if the programmer was forced to pay more attention to this, they would get it right. We all know that good UI (just like good anything) doesn't come free.

Aaron Brethorst

Jan - I've opened a suggestion on the MSDN Product Feedback Center, which is our public bug tracking system for Visual Studio, WinFX, and the .NET FX (which includes Winforms) for consideration in Orcas.


Thanks for the suggestion!
Aaron Brethorst
Ux Program Manager
Visual Studio Core

Ben Karel

In the same light, it would be enormously valuable for WYSIWYG HTML editors or a client UI designers to offer some way to point to a visible element and ask, "Why is this thing ending up with the position and size that it has?"

It's more geared towards web developers, but for the past five or so years, Mozilla browsers have been able to do that for web pages. The DOM Inspector (under the Tools menu) lets you select arbitrary elements in a page and see all the CSS selectors and associated rules that are being applied to the element. (Plus other nice things, like all the attributes set on that node. Quite useful.)


...and even better than that, the Web Developer toolabr for Firefox and Mozilla lets you edit that kinda stuff on the fly (I think it does a page reflow when you hit newline), so you can *immediately* see the consequences of any particular change.

Peter Centgraf

Andy Ko at the Carnegie Mellon HCI Institute has done this for visual 3D programming. He calls it the "Whyline".


The comments to this entry are closed.