Re: Set resolution (was ARGGGGHHH!......pls help!)

[Bruce Epstein - Zeus Productions]

I misspoke. I meant to write:

You can check and store the old refresh rate before switching the
resolution. When switching to a new resolution, I don't specify a refresh
rate. I let the monitor do that itself (that is, I accept the default rate).

I typically ask the user whether they want to change the monitor and then
automatically change it back when they quit. I've yet to encounter a case
where Buddy has misreported whether the monitor could be changed without a
reboot. Therefore, I don't usually ask the user to confirm that it worked
after the switch. If Buddy reports that the new resolution is not supported
without a reboot, then I don't even try to change it. I just recommend that
the user quit and set their resolution manually before running the
presentation again.

However, when returning to the original resolution, I specify the original
refresh rate as well, to assure that the original settings are reinstated.
This seemed to be required on one NT system where the refresh rate was
different by default when *returning* to the original resolution than it
was at the outset. Thus, the error only occured when my program exited, but
this is perhaps just a coincidence. I could well have ran into a problem
when setting the resolution, I suppose.

The real fun is trying to get epilectics to convulse by making their
monitor flicker (I kid the epilectic.)

Bruce

At 12:50 PM -0400 05/08/01, Lingo-L Digest wrote:
>
>>Gary Smith, makes of buddy, has a version of baSetDisplay that sets the
>>monitor refresh rate too. I guess it would be best to check the old refresh
>>rate and use that as the new refresh rate when changing the resolution.
>
>
>Not really. If they are on 800 x 600, 100 Hz, that's 60 KHz or so.
>Setting to 1280 x 960 at 100 Hz would be 96 KHz, almost certainly too
>high for most monitors. If you see what the current horizontal scan
>rate is and try to mimic that, you would be safer. For example, 60
>KHz divided by 960 lines would be 62.5, so you could safely set the
>rate to 60 Hz, and perhaps chance 72 or 75 Hz.


---------
Looking for an ActionScript book as good as Lingo and Director in a
Nutshell? Check out "ActionScript: The Definitive Guide" from O'Reilly.
Written by Colin Moock, edited by Bruce Epstein. Available Now!
http://www.amazon.com/exec/obidos/ASIN/1565928520/zeusproductions
--------



[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi  To post messages to the list,
email [EMAIL PROTECTED]  (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo.  Thanks!]