Re: Top-10 Accessibility API Wish List
Re: Top-10 Accessibility API Wish List
- Subject: Re: Top-10 Accessibility API Wish List
- From: Eric Schlegel <email@hidden>
- Date: Wed, 11 Sep 2002 23:12:54 -0700
On Wednesday, September 11, 2002, at 10:57 PM, Michael Kamprath wrote:
Just out of curiosity, OS X has Cocoa and Carbon API's, and WNE-based
apps
are really Carbon Event apps layered on top of the Carbon Event model.
I'm
going to assume Classic apps are what you are talking about as
"non-Carbon
Event" windows, or is there are third type of application (Java
Swing???)
that aren't Cocoa-based or can't understand Carbon Events?
No, Guy is talking about WNE-based apps here. If the app is
Carbon-event-based, it's easy for us to send a kEventWindowClose event
to the window, and the app should respond to that as if the close box
had been clicked. If the app is WNE-based, however, at a minimum we
would need to post a mouse-down/mouse-up pair over the close box in
order to fool the app into thinking that the user had clicked on the
close box, and depending on the app, even that might not be enough.
That's the "puppet stringing" that Guy is referring to.
supported by Accessibility - after all, Classic is dead, right? - but
Carbon
Event application really should be fully supported. And that is
exactly what
my request is (no more).
It's easy to support fully Carbon-event-based apps. The problem is that
today, most Carbon apps are not Carbon-event-based; they still use WNE.
That's much harder.
-eric
_______________________________________________
accessibility-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/accessibility-dev
Do not post admin requests to the list. They will be ignored.