gkearney wrote:I have no idea I just downloaded the open source QT and tired the samples, none worked. In the Cocoa environment things are accessible out of the box but there are thing u can do to improve the usage.
I don't know exactly how it works, but the documentation indicates that it's purposefully a plugin system so that there is no performance penalty for standard users. I know that Qt does use Cocoa on Mac, I've just never had to go the accessibility route.
OK, I just figured it out. Try the following, assuming you're on Linux or Mac:
The accessibility plugin should be in:
$INSTALLDIR/plugins/accessible/libqtaccessiblewidgets.so
But, you also have to configure the examples to use the plugin, so go to the .pro file for the example that you want to try and add the following line near the top:
Then re-run qmake and make. That will link the accessibility library in.
As long as the plugin is in your library path, it should work. Just to be sure:
Code: Select all
$ export LD_LIBRARY_PATH=$INSTALLDIR/plugins/accessible/libqtaccessiblewidgets.so
$ ldd ./yourExample | grep accessible
libqtaccessiblewidgets.so => /usr/lib/qt4/plugins/accessible/libqtaccessiblewidgets.so (0xb7ec9000)
I also verified that the shared library was opened when running the example:
Code: Select all
# lsof | grep <pidOfMyProg> | grep accessible
mdi 19173 kibab mem REG 3,6 205524 12001561 /usr/lib/qt4/plugins/accessible/libqtaccessiblewidgets.so
I think this implies that any truly custom widgets (eg. any widget not composed of native widgets) would have to be written in C++, even if we were to use PyQt, but the above shared library works with all the builtin widgets, and the number of truly custom widgets is usually minimal (at least for the programs I have done).
Let me know how it goes.
--kpederson