I think it was always the lack of a portable API for toolkit vendors to program. I’m sorry that Apple never did that; it’s clearly been an impediment not otherwise necessary to overcome on other platforms. It’s not always possible to subclass or overload, so you need to handle accessibility events directly and that means you have to talk to the Objective-C runtime and hence carry a lot of very specific code to implement accessibility properly. Not impossible but much more work so it doesn’t happen as often, or at all, compared to other more portable binary-compatible interfaces that’ll get implemented in portable programming languages.
-- The following information is important for all members of the Mac Visionaries list. If you have any questions or concerns about the running of this list, or if you feel that a member's post is inappropriate, please contact the owners or moderators directly rather than posting on the list itself. Your Mac Visionaries list moderator is Mark Taylor. You can reach mark at: mk...@ucla.edu and your owner is Cara Quinn - you can reach Cara at caraqu...@caraquinn.com The archives for this list can be searched at: http://www.mail-archive.com/macvisionaries@googlegroups.com/ --- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To unsubscribe from this group and stop receiving emails from it, send an email to macvisionaries+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/macvisionaries/8843A044-1AEB-4608-87EF-743F103C730E%40me.com.
