Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!husc6!endor!siegel
From: siegel@endor.harvard.edu (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Have you had problems with SetClikLoop?
Message-ID: <3509@husc6.harvard.edu>
Date: 29 Dec 89 03:36:19 GMT
References: <921@excelan.COM> <3429@hub.UUCP>
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Organization: Symantec Language Products Group
Lines: 36

In article <3429@hub.UUCP> 6600pete@hub.UUCP writes:
>From article <921@excelan.COM>, by mahboud@kinetics.com (Mahboud Zabetian):
>> Hi.  Anybody out there ever try calling SetClikLoop twice consecutively for
>> different TEHandles?  I am doing so and it seems that the second call also
>> changes the value of the clikLoop field of the first TE!  Sound strange?
>
	SetClikLoop saves away the old clickLoop in a place relative to
A5, so that it can restore it. When and why, I don't know. Because TE
doesn't maintain a stack of saved clikLoops, it will smash old ones,
as you're finding out.

	The simplest workaround is to not use SetClickLoop but instead
to just store the clickLoop field directly. I don't know what the implications
are, if any, so maybe someone from Apple who *knows* TE can shed some light.

>I got this info from Michael Kahl, who apparently wrote a substantial portion
>of TE (if I read him correctly). Here's a code fragment in Pascal:

	I don't know if Mike Kahl would be insulted or not to be associated
with TE in this fashion. ;-) For the record, he wrote THINK C, not TE.

R.



~~~~~~~~~~~~~~~
 Rich Siegel
 Staff Software Developer
 Symantec Corporation, Language Products Group
 Internet: siegel@endor.harvard.edu
 UUCP: ..harvard!endor!siegel

"When someone who makes four hundred and fifty dollars an hour wants to
tell you something for free, it's a good idea to listen."

~~~~~~~~~~~~~~~