I'm designing a windows app with MFC whose main frame window cannot be resized or dragged. The window is initialized to be maximized and remains so throughout it's use, refusing to be resized. It can be minimized to taskbar and restored. In essence, the app's window is full-time maximized.
The question is, would the average user find this type of design very inflexible? Would such design be frowned upon by the authorities of good design?
Frankly, I hate applications that block normal Windows functionality. I don't even tolerate games that do that. I've so many times encountered demos of very nice games where for instance alt-tab is blocked or where it's impossible to run them in windowed mode. Do you think I've bought any of those games?
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are, by
definition, not smart enough to debug it.
- Brian W. Kernighan
The question is, would the average user find this type of design very inflexible? Would such design be frowned upon by the authorities of good design?
I'd say the question is why do you want to have this functionality? If there's a good reason for this, then the question becomes: is it good for you or for the user? If there's no good reason then don't do it. Too many people try to make their application 'special' by making it different from other applications. Or they add some weird feature that they really love. All that really does is make the application hard to use.
You should aim for your application to behave like most users would expect it to behave. Most of the time that means behave like most other programs, but special circumstances can call for a special approach.
Cheers, D Drmmr
Please put [code][/code] tags around your code to preserve indentation and make it more readable.
As long as man ascribes to himself what is merely a posibility, he will not work for the attainment of it. - P. D. Ouspensky
Bookmarks