>Jeff (and Bruce, since you suggested a similar strategy)-
>
>I think this strategy is severely politically incorrect. If a user has his screen resolution set to 640x480, it is because that user wants to see everything large. He can go around his entire operating system and look at every application, and nearly all will have similar or identiacally sized textboxes, fonts, buttons, etc. Then he goes to your app, which just resized all of its elements to cram all the controls you deemed necessary to fit in the user's tiny screen. Now your app is the only app on the machine with small buttons and text. And the only app in which the far-sighted use has to squint to read the UI. The same goes for users with unusually high resolutions- I set my resolution high because I like to fit a lot of stuff on the screen. But your app just blew itself up to cover my valuable screen real-estate, negating all the benefits of my huge monitor.
>
>Is this really what you want to do to your users? Didn't they make the size decision when they set their resolution in the first place?

I'm not quite sure what you mean, Erik - What I'm saying is to design at 640, and then enlarge for higher res. As it is now at 640, without resizing, people need to squint to see at 1024. It doesn't require huge enlargement of forms/contained objects, such as to fit the entire screen at 1024, just enough to make it more usable.