Prev: Parsing XML in string variable?
Next: instrumentation in enterprise ibrary.
From: Arne Vajhøj on 11 Feb 2010 21:31
On 11-02-2010 15:11, Chris Dunaway wrote:
> Arne showed you the Windows API call to change the screen resolution,
> but please don't do that! The user has set their resolution to what
> they like and you should not change it! You might have the intent of
> changing it back when you are through, but if your program crashes,
> then the user will have to change it back manually.
>
> Generally speaking, it is bad form to change any of the user's desktop
> settings.

I can not see any need to change it either.

But the original poster must have had some idea with it.

Arne


From: Scott M. on 12 Feb 2010 10:16

"Arne Vajh�j" <arne(a)vajhoej.dk> wrote in message
news:4b74bd69$0$273$14726298(a)news.sunsite.dk...
> On 11-02-2010 15:11, Chris Dunaway wrote:
>> Arne showed you the Windows API call to change the screen resolution,
>> but please don't do that! The user has set their resolution to what
>> they like and you should not change it! You might have the intent of
>> changing it back when you are through, but if your program crashes,
>> then the user will have to change it back manually.
>>
>> Generally speaking, it is bad form to change any of the user's desktop
>> settings.
>
> I can not see any need to change it either.
>
> But the original poster must have had some idea with it.
>
> Arne

It may be for something like a video game, where there is an "Options"
section that allows the user to change resolution for the duration of the
game. It could be that the resolution change is actually initiated by the
user of the program and then the program returns the resolution back to its
original state when the program exits.

You are both right that this shouldn't be done without the user's consent,
but there may well be perfectly acceptable reasons to do it with the user's
concent.

-Scott


First  |  Prev  | 
Pages: 1 2
Prev: Parsing XML in string variable?
Next: instrumentation in enterprise ibrary.