Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!seismo!dimacs.rutgers.edu!rutgers!cbmvax!peter From: peter@cbmvax.commodore.com (Peter Cherna) Newsgroups: comp.sys.amiga.programmer Subject: Re: Mouse blanking Message-ID: <21447@cbmvax.commodore.com> Date: 9 May 91 16:20:07 GMT References: <9107@crash.cts.com> <91127.171511DXB132@psuvm.psu.edu> Reply-To: peter@cbmvax.commodore.com (Peter Cherna) Organization: Commodore-Amiga, Inc. West Chester, PA. Lines: 48 In article dillon@overload.Berkeley.CA.US (Matthew Dillon) writes: > Nope, doesn't work. A couple of problems with SetPrefs(): > > (1) Takes an incredible amount of CPU. Not something you want > to do very often. And it's slower under 2.0, because its job is much harder. > (3) Obsolete under 2.0, though probably still works for pointer data. Under 2.0, Preferences has been broken into multiple subsystems, which are sometimes equivalent to but often leagues beyond what could be set through SetPrefs(). SetPrefs() still works where the old-style information is known to be meaningful. Where the old style information could wipe out new information it couldn't know about, it's ignored. Here are a few examples: * Printer. No new Preferences items were added. SetPrefs() is fully equivalent. * Colors. Preferences contains 7 colors (four for the WB, three for the pointer). These take effect as before, even though the new Preferences allows you to set all the colors of the WB, even if that means 16. * FontHeight. Under 1.3, this could be 8 or 9. Under 2.0, you get to specify font names and size. Thus FontHeight is ignored, since it'll always contain 8 or 9, and you don't want to lose your nice Helvetica 15 just because someone did a SetPrefs(). * Pointer. 2.0 pointers can be taller. If you do a GetPrefs(), you'll receive the first 16 lines in the structure you get back. If you did a SetPrefs() and Intuition listened to it, it'd chop off your pointer. Here the rule is: the pointer part of SetPrefs() is followed until the first new-style pointer is seen, and ignored thereafter. So the answer is: when reasonable and possible, SetPrefs() is still heeded. Those pieces of SetPrefs() that would interfere with new 2.0-style preferences are ignored. > Matthew Dillon dillon@Overload.Berkeley.CA.US Peter -- Peter Cherna, Operating Systems Development Group, Commodore-Amiga, Inc. {uunet|rutgers}!cbmvax!peter peter@cbmvax.commodore.com My opinions do not necessarily represent the opinions of my employer. "If all you have is a hammer, everything looks like a nail."