Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site sdcc13.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!bellcore!decvax!tektronix!hplabs!sdcrdcf!sdcsvax!sdcc3!sdcc13!ee163ahe From: ee163ahe@sdcc13.UUCP (VICTOR ROMANO) Newsgroups: net.micro.mac Subject: Bug in TESetSelect (first text operation only) Message-ID: <168@sdcc13.UUCP> Date: Mon, 4-Mar-85 21:24:18 EST Article-I.D.: sdcc13.168 Posted: Mon Mar 4 21:24:18 1985 Date-Received: Sun, 10-Mar-85 07:28:28 EST Organization: U.C. San Diego, Academic Computer Center Lines: 23 There is an interesting bug in TESetSelect. If it is called before TEClick is ever called, the selection region is set to the proper value, but the caret appears at the end of the previous line if it was intended to appear at the beginning of a line. Of course this causes strange things to happen when something is inserted (an in TEKey). There is an interesting kludge which I added to solve this problem: (using MegaMax C) if ((*hte)->clickstuff == 0) (*hte)->clickstuff = -1; tesetselect (start, end, hte); I discovered this is because clickstuff always has a value of -1, -255, -256, 255, and 256, but 0 before any text operations have been performed. I arbitrarily chose to assign the value of -1, since this is the most common. Question: can this have any harmful side effects? Also, what does this field mean, anyway? Victor Romano