Re: NSTextView's MarkedText
Re: NSTextView's MarkedText
- Subject: Re: NSTextView's MarkedText
- From: Gordon Apple <email@hidden>
- Date: Mon, 22 Jul 2013 19:22:38 -0500
- Thread-topic: NSTextView's MarkedText
Thanks for the direct reply. The summaries are few and far between,
possibly a result of the dev-site outage.
My speculation had to do with the highlighting I am trying to do. I
currently support setting the background color of selected text. However, I
would like to have the equivalent of a highlight pen, where the user selects
a highlight color and then drags across the text. I cache the current
selection highlight color, then change the selection highlight to the chosen
color. The intent (not completely implemented yet) is, on mouseUp, to then
set the background color, deselect the text, and restore normal
highlighting. I have created an augmented iBeam cursor (including a color
patch), but have had difficulty getting the text cursor to switch from the
iBeam to mine.
I was thinking that, if markedText worked the way I was speculating, maybe
it would be a way to do the pen highlighting, and also allow all markings to
be easily cleared for the entire text view, if desired. Thus, my other
questions.
On 7/22/13 6:45 PM, "email@hidden"
<email@hidden> wrote:
>
>
> Sent from my iPhone
>
> On 2013/07/23, at 7:38, Gordon Apple <email@hidden> wrote:
>
>> > Extensive Googling has not produced an answer. What is a MarkedText
>> > attribute? Is setting a background with markedText the same as just
>> setting
>> > the (selected) text background? Or does markedText take precedence over >>
(or
>> > overlay) text background? Is this permanent or temporary, i.e., does the
>> > marked text attribute get archived with the attributed string? Is
>> > markedText simply a way to categorize marking attributes, so that they can
>> > easily be identified and cleared from the text?
>> > _______________________________________________
>> >
> Marked text in Cocoa is mainly used by input methods. Primarily with languages
> that have more glyphs than you would have on a keyboard and input is done in a
> form that is analyzed and is provided a set of conversion options. a range of
> input text that is not yet committed is highlighted and commonly sub ranges
> can be selected and converted. When conversions are selected and finalized
> text is unmarked and ready for committing.
>
> Japanese, Chinese and Korean are the most commonly encountered. Each with more
> than one input approach.
>
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden