Re: UIAccessibilityAnnouncementDidFinishNotification reliability
Re: UIAccessibilityAnnouncementDidFinishNotification reliability
- Subject: Re: UIAccessibilityAnnouncementDidFinishNotification reliability
- From: Chris Fleizach <email@hidden>
- Date: Fri, 09 Aug 2013 11:09:30 -0700
You should always get the call back for each announcement you send. If you're not seeing them, then it's probably a bug (when they're cancelled, you should see the flag changed, instead of not seeing them)
Thanks
On Aug 7, 2013, at 2:38 PM, Doug Russell <email@hidden> wrote:
> Just to give some context, this is a project where I'm trying to add some context for moves between text fields using announcements:
>
> http://cl.ly/3V0k1w22053F
>
> It works pretty well until you do any kind of button mashing after activating a text field and then the notification gets dropped and the announcement queue stalls.
>
> On Aug 7, 2013, at 2:01 PM, Doug Russell <email@hidden> wrote:
>
>> What are the rules for when UIAccessibilityAnnouncementDidFinishNotification does and doesn't fire?
>>
>> I can get it to not fire pretty reliably by tapping on another element after I've called post notification, before it can actually start it's announcement.
>>
>> I'm trying to queue up a couple announcements in a row and I'd like them not to step on each other, but without a reliable way to know when to fire the next announcement, this doesn't seem feasible.
>
>
> _______________________________________________
> 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
_______________________________________________
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