On Thu, Feb 21, 2008 at 9:40 PM, Ben Lowery <[EMAIL PROTECTED]> wrote: > On Wed, Dec 5, 2007 at 11:02 AM, Peter Jones <[EMAIL PROTECTED]> wrote: > > Adrian Robert wrote the following on Wed, Dec 05, 2007 at 07:28:49AM +0300: > > > > > One question: are you able to observe the bug when there is only ONE > > > active frame with ONE active window? > > > > I first noticed this problem in rc2, with only one frame and one > > window. I'm back on rc2 now (because of emacsclient) and will post a > > screenshot of this if I see it. > > > > P.S., I'm also running on leopard (which was a huge mistake). > > Did anyone ever get a chance to look into this? I see it daily on > 10.5.2. I'd be happy to dig around in the code a bit if I knew where > to start looking....
ns_draw_window_cursor() in nsterm.m draws the cursor and is also responsible for erasing during blink cases. Cursor blink itself is handled by [EmacsApp -cursor_blink_handler:] in that same file, which is called periodically during event processing. It uses kind of a hack by calling update_window_cursor(). Ideally this would be removed and the code switched to use emacs core's standard means for doing cursor blink. (The reason for the different impl is blinking cursors were supported by this port before emacs itself supported them.) ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Emacs-app-dev- mailing list Emacs-app-dev-@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emacs-app-dev-
