RE: To notify or not...
RE: To notify or not...
- Subject: RE: To notify or not...
- From: Charlie Powell <email@hidden>
- Date: Tue, 29 Nov 2016 00:49:28 +0000
- Thread-topic: To notify or not...
I believe this matters for the accessibilitySelectedTextRange property, so if the user moves the insertion point (IP) via some shortcut like Alt+Right arrow, then you should only be raising a selection changes notification and *not* a value changed notification.
Typing is a little more interesting... you certainly want to raise the value changed notification (the value did change, after all), but should you raise a selection changed notification? We have in our apps since the actual NSRange values you'd give back for accessibilitySelectedTextRange will be different (range.location will be 1 greater than it was previously). This does seem a little inconsistent with other parts of AppKit though - we prototyped some things with NSTextViews and found that when you type in a text view, the textDidChange: delegate method gets called, but the textViewDidChangeSelection: delegate method does *not*.
----------------------------------------------------------------------
Message: 1
Date: Mon, 28 Nov 2016 16:23:05 +0000
From: Tim Burgess <email@hidden>
To: "'Accessibility-Dev Accessibility-Dev Mail'"
<email@hidden>
Subject: To notify or not...
Message-ID: <000201d24993$b2ff1f50$18fd5df0$@raisedbar.net>
Content-Type: text/plain; charset=utf-8
Hi all,
Can I just clarify whether or not I need to raise a value change notification and/or a selection change notification when the insertion point moves? Part of me says that the cursor location is effectively part of my document data and part says not:)
Best wishes.
Tim Burgess
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden