home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cis.ohio-state.edu!rutgers!concert!borg!strauss!lari
- From: lari@strauss.cs.unc.edu (Humayun Lari)
- Newsgroups: comp.sys.mac.programmer
- Subject: Re: Keeping the cursor visible
- Message-ID: <14961@borg.cs.unc.edu>
- Date: 2 Sep 92 21:54:21 GMT
- References: <Btwnq8.LMv@mentor.cc.purdue.edu> <15119@claris.com>
- Sender: news@cs.unc.edu
- Organization: The University of North Carolina at Chapel Hill
- Lines: 20
-
- In article <15119@claris.com> wombat@claris.com (Scott Lindsey) writes:
- >In article <Btwnq8.LMv@mentor.cc.purdue.edu>, neath@brazil.psych.purdue.edu (Ian Neath) writes:
- >>
- >> writes to the TextEdit record, the cursor is hidden by (I assume) a
- >> call to ObscureCursor. Is it OK to keep calling ShowCursor ...
- >
- >ShowCursor won't actually show the cursor if it's only obscured. I don't
- >think there's a legal way to unobscure a cursor, however, setting the low-
- >memory global CrsrNew = 0xFF forces it to really redraw.
-
- If you're in charge of the writes to the TextEdit record (i.e. using TEKey),
- you could use TEInsert instead to prevent TextEdit from trying to be polite
- and calling ObscureCursor. Of course, TEInsert may be a bit slower, but in
- practice it seems to make little difference. And it's definitely *much* cleaner
- than having the cursor flicker every time a character is appended to the TE
- record (especially if you're porting a MS-DOS-based language interpreter that
- thinks a row of dots on the screen is a beautiful depiction of its progress).
-
- Humayun Lari
- (lari@cs.unc.edu)
-