Path: utzoo!attcan!uunet!ncrlnk!ncrcae!hubcap!gatech!rutgers!apple!bionet!agate!helios.ee.lbl.gov!ux1.lbl.gov!osborn
From: osborn@ux1.lbl.gov (James R Osborn)
Newsgroups: comp.sys.mac.programmer
Subject: LSC 3.0-QuickKeys and QuickDraw
Summary: LSC/QuickKeys Prob.s + QuickDraw/PICT etc. Questions
Keywords: LSC QuickKeys QuickDraw PICT
Message-ID: <1250@helios.ee.lbl.gov>
Date: 11 Nov 88 18:59:19 GMT
Sender: usenet@helios.ee.lbl.gov
Reply-To: osborn@ux1.lbl.gov (James R Osborn)
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 84


--------------------------------------------------
LightSpeed C version 3.0p2 with QuickKeys PROBLEMS:
--------------------------------------------------

	(1)  Has anyone had any problems with QuickKeys MOUSIES not
operating properly with LSC 3.0?  My Page Up and Page Down are having
problems, ie. the cursor jumps to the proper place, but no action.
The Home and End work fine.  This is true within LSC running the program
and with the resulting stand-alone application.  Also, using the ~ as
the definition for the close window MOUSIE, sometimes LSC bombs
unpredictably.  Sometimes it happened from the running program, and
at other times in the LSC editor.  (More frequently the latter.)

	(2)  Another problem has to do with QuickKeys intercepting
command-Q or other menu-key definitions and reporting that it cannot
find the menu selection EVEN when command-Q has NOT been used for
a QuickKey definition!?  (I only noticed this in LSC with some projects.)


	I would be interested if anyone knows about these types of
problems:  are they LSC problems or QuickKeys?  (I happen to think
the latter, but one never knows.)  AND if there happens to be any
word on whether any cures are available.


-------------------
QUICKDRAW Questions:
-------------------

	(1)  Does anyone know if it is possible to cause the window
	manager to erase the space occupied by moved (etc.) windows
	with black instead of white?  I remember reading somewhere
	that the Wmgr accumulates the regions of various windows that
	are affected, and then sets that entire region to white.  For
	cGrafports this isn't done since different windows might have
	different background colors.  But what about getting the old
	QuickDraw/Wmgr's to erase to black instead of white?

	(2)  Along a similar note, the old QuickDraw color definitions
	default to BLACK on black and white devices while they are
	shown as colors on a color Mac II.  Is there some hook, or
	kludge that can be used to tell QuickDraw to use white as the
	default color instead of black?

	The current of these questions is (if you haven't guessed it
	already):  I would like to display color PICT files (using
	the OLD QuickDraw colors) in an old grafport on a B/W machine
	with a BLACK background.  The colors should show up as white
	on a B/W machine, while they should show up in color on a color
	Mac II.  As it stands, if I have a black background, and the
	colors default to black, I get (guess what?) a black window!
	I believe the color case will already work properly. Ideally,
	it would be nice to be able to toggle this so the user could
	choose either white (or color) on black OR black (or color) on
	white - get it?

	(3)  One other typical problem:  Yes I too have experienced
	the PICT Clip Rect overflow when the display Rect coordinates
	are offset too much relative to the coordinates of the clip
	Rect.  (It's times like these that I wish window coordinates
	were long integers...)  Anyway, the solution of setting the
	clipping just after opening the Picture is fine if YOU are
	creating the Picture.  But what if you are reading some other
	application created PICT which either left the clipping maxed
	(by default) or just as unfortunately set it such that the
	display rect you specify still causes a clip rect overflow?
	Is there some way to restore the clipping to the max size
	(i.e. - to the whole window) after starting to do the
	DrawPicture (after the clip has become an empty rect), BUT
	before any drawing has taken place?


-----------------------------------------------------------------------
Feel free to email me, or post if appropriate.

	|------------------------------|
	| James R. Osborn              |
	| Lawrence Berkeley Laboratory |
	| osborn@ux1.lbl.gov           |
	|------------------------------|

P.S.  This porgram will not be for profit if that matters to anybody.
I expect to hear from the G-Ds (Horvath isn't it?).