[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Use Core Text for Cocoa Emacs

From: Jason Rumney
Subject: Re: Use Core Text for Cocoa Emacs
Date: Thu, 20 May 2010 13:58:06 +0800
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20100111 Lightning/1.0b1 Thunderbird/3.0.1

On 20/05/2010 10:59, address@hidden wrote:
If I activate VoiceOver from the System Preferences as described above
and click the Emacs frame, then the whole content area (i.e., other
than the title bar and the tool bar, but including scroll bars) of the
frame gets bordered in black, and the application name ("Emacs"), the
title bar name, and the buffer text get spoken in this order.  But the
cursor keys do not cause the character under the cursor to be spoken.

If this is heading to the right direction, then Core Text vs. NS Text
system, both of which are used in the Mac port, has basically nothing
to do with accessibility.
Yep, you are going in the right direction -- menues, prompts, buttons
and all such should be spoken.  Look at the system preferences dialog
and you will get an idea.  Look at textedit and you will get an idea of
what we  would like the cursor to do.

Is this because Emacs draws its own cursor?

On Windows, accessibility functions were made to work by introducing the variable `w32-use-visible-system-caret' and its associated code in w32fns.c/w32term.c. When the user sets that variable to non-nil, the Windows caret is used, which allows Accessibility tools to track the cursor position and read text at the cursor, at the expense of losing user customization of the visual look of the text cursor.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]