[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
QuickDraw arcs again
- To: email@example.com, firstname.lastname@example.org
- Subject: QuickDraw arcs again
- From: Ranson <ranson@LANNION.cnet.fr>
- Date: Mon, 25 Oct 1993 03:29:00 +0000
- X400-content-type: P2-1984 (2)
- X400-mts-identifier: [/PRMD=CNET/ADMD=ATLAS/C=FR/;email@example.com]
- X400-originator: ranson@LANNION.cnet.fr
- X400-received: by mta mhs-relay.cs.wisc.edu in /PRMD=XNREN/ADMD= /C=US/; Relayed; Mon, 25 Oct 1993 02:29:24 +0000
- X400-received: by /PRMD=inria/ADMD=atlas/C=FR/; Relayed; Mon, 25 Oct 1993 02:29:18 +0000
- X400-received: by /PRMD=CNET/ADMD=ATLAS/C=FR/; Relayed; Mon, 25 Oct 1993 03:29:00 +0000
- X400-recipients: non-disclosure:;
I just got hit by the arc bug myself. Looking back in the archives, the
conclusion on the subject was that the culprit was SuitCase. I *don't* use
The call I use is (#_FrameArc rect start-angle arc-angle). I've checked that
the values I pass are correct. If I break into MacsBug just beofre the trap i
called and look at the stack, I find that the rectangle is correct, but that
random values are passed for the angles ! Indeed, if I patch the values at
this time, the arc is drawn correctly.
So the problem seems to be in the trap calling code in MCL. The definition of
_framearc looks correct, so this leaves us with deftrap.
Any ideas ? workarounds ? patches ?