From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Abrahams Newsgroups: gmane.emacs.devel Subject: Who can explain the display architecture? Date: Thu, 14 Jul 2005 14:55:01 -0400 Message-ID: References: <1117787455.42a0153fdf46f@webmail.freedom2surf.net> <1118072836.42a47004de422@webmail.freedom2surf.net> <1118265839.42a761ef2be05@webmail.freedom2surf.net> <1118304628.42a7f974aab30@webmail.freedom2surf.net> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1121368011 32243 80.91.229.2 (14 Jul 2005 19:06:51 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 14 Jul 2005 19:06:51 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 14 21:06:50 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Dt91j-0007sB-ED for ged-emacs-devel@m.gmane.org; Thu, 14 Jul 2005 21:05:43 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dt93T-0001dj-FT for ged-emacs-devel@m.gmane.org; Thu, 14 Jul 2005 15:07:31 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Dt92P-0001JD-J8 for emacs-devel@gnu.org; Thu, 14 Jul 2005 15:06:25 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Dt92J-0001FL-VP for emacs-devel@gnu.org; Thu, 14 Jul 2005 15:06:22 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dt92I-0001Bi-Lb for emacs-devel@gnu.org; Thu, 14 Jul 2005 15:06:18 -0400 Original-Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtp (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.34) id 1Dt90I-0002V9-Vs for emacs-devel@gnu.org; Thu, 14 Jul 2005 15:04:15 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Dt8rw-000661-4m for emacs-devel@gnu.org; Thu, 14 Jul 2005 20:55:36 +0200 Original-Received: from 146-115-127-135.c3-0.smr-ubr2.sbo-smr.ma.cable.rcn.com ([146.115.127.135]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 14 Jul 2005 20:55:36 +0200 Original-Received: from dave by 146-115-127-135.c3-0.smr-ubr2.sbo-smr.ma.cable.rcn.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 14 Jul 2005 20:55:36 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 47 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 146-115-127-135.c3-0.smr-ubr2.sbo-smr.ma.cable.rcn.com User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (windows-nt) Cancel-Lock: sha1:bcKHLSiBK1AVcP0bP446zPukOSU= X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:40891 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:40891 I am trying to get a clue as to how this stuff is organized so that I can fix the problems described below. Thanks for your attention. David Abrahams writes: > This concerns the one remaining problem with the ClearType patch I'm > trying to clean up and submit. I hope I don't seem too insistent, but > I've been trying to get a hint for about a week. > > David Abrahams writes: > >> David Abrahams writes: >> >>> David Abrahams writes: >>> >>>> I am seeing some minor artifacts that I don't know what to do about. >>>> For example, when I backspace over these parens starting from the end >>>> of the line, I end up with some small remnants of the background color >>>> emacs uses to highlight matching parens for me. When all the close >>>> parens are gone there's a thin vertical cyan line at the right edge of >>>> each open paren. Any clues where to attack that? >>>> >>>> ((((())))) >>> >>> Even some vague hints would be a big help here. This is the only >>> remaining detail as far as I can tell. >> >> I have one more piece of information for anyone who can think about >> this problem for a moment: When I do `C-s x', the first instance of x >> (or whatever character) that is found gets highlighted in purple and >> looks right. The next instance of x on that line gets highlighted in >> cyan and looks right. The rest of the instances of x on that line get >> highlighted in cyan, and the highlighting extends one pixel too far to >> the left. On each line thereafter, the first instance of x is >> highlighted in cyan and looks right, and the rest of the instances on >> that line are highlighted in cyan and look wrong (i.e. the >> highlighting extends one pixel too far to the left). > > Can someone please give me some hint as to which entry points to > breakpoint in order to observe these calculations and/or drawing in > action? -- Dave Abrahams Boost Consulting www.boost-consulting.com