Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!samsung!crackers!m2c!umvlsi!umaecs!amh!djvelleman
From: djvelleman@amherst.bitnet
Newsgroups: comp.sys.mac.programmer
Subject: Re: clikLoop -- Unclear on the concept
Message-ID: <12115.27c4e2f3@amherst.bitnet>
Date: 22 Feb 91 09:22:59 GMT
References: <2305.27c2a58c@spacm1.spac.spc.com> <1991Feb21.043729.25610@bootsie.uucp>
Lines: 24

In article <1991Feb21.043729.25610@bootsie.uucp>, olson@bootsie.uucp (Eric K. Olson) writes:
> In article <2305.27c2a58c@spacm1.spac.spc.com> audit038@spacm1.spac.spc.com writes:
>>In using my own clikLoop function with TE records I came up with the following
>>problem:
>>
>>Window A has a TE record with a ptr to clikLoop A. (works fine)
>>Create Window B with another TE record and clikLoop B.
>>
>>Now when I return to window A,  clikLoop A is no longer called.
>>
>>If I put a SetClikLoop in my window update routine (i.e every time the
>>window becomes active I reset the clikLoop ptr) the clikLoop routine is once
>>again called.
> 
> This is a misfeature of the glue provided by Apple for SetClikLoop().
> This misfeature occurs in THINK C and MPW C (because they both use
> Apple glue).  To avoid the problem, don't use SetClikLoop().  Instead,
> use this:

  Does anyone know if there are similar problems with WordBreak routines?  I
once tried to install my own WordBreak routine, and could never get it to
work, and could never figure out why.

  -Dan Velleman