> On Sep 18, 2015, at 21:24, Quincey Morris > <quinceymor...@rivergatesoftware.com> wrote: > > On Sep 18, 2015, at 16:46 , Alex Hall <mehg...@icloud.com > <mailto:mehg...@icloud.com>> wrote: >> >> myField.accessibilityHelp="new help message" >> > > Well, it’s a fascinating problem. I can see what’s wrong, but I don’t know > why. > > For some reason, the “accessibilityHelp” property, declared in the > NSAccessibility protocol, is being bridged into Swift as a function (well, 2 > functions, a getter-alike and a setter-alike), rather than a Swift property. > The following syntax compiles: > > myField.setAccessibilityHelp (“new help message") > > though I have no quick way of verifying that it’s doing the right thing at > run-time. AFAICT this has nothing to do with the text field being an outlet. > > You should submit a bug report.
Thanks for that; yes, I will file one. During execution, the hint works perfectly when set that way. How odd. FYI, with VoiceOver enabled, pressing control-option-shift-h will speak the hint (AKA help) for whatever item is in focus. Control-option-f3 will speak the accessibility text. Just in case you ever need it for testing, but then again, I guess you'd be able to use the Accessibility Inspector instead. -- Have a great day, Alex Hall mehg...@icloud.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
