On Thu, 2011-03-24 at 20:51 +0000, Caolán McNamara wrote:
Following the usual naming scheme the XAccessibleEventBroadcaster
add/remove on should have been named
[add|remove]AccessibleEventListener in the first place, I guess we're
stuck with that one now.
Hmm - are those interfaces published ? and if so why ? you'd have to be
pretty barking to interact directly with our UNO a11y APIs outside the
tree, rather than using IAcc2 / atk / Java remotely.
So - it'd be a chunk of work of course; but if this is the only big
thing blocking us turning on a very valuable warning, I'd (personally)
say we should just bite the bullet and un-publish & tweak this
interface.
Then again, if this is only part of the problem, perhaps it is
un-fixable, though we could (perhaps) use some 'orrible gcc-specific
hack:
#ifdef GCC
#pragma GCC diagnostic ignored "-Woverloaded-virtual"
#endif
or something ? ;-)
ATB,
Michael.
--
michael.meeks@novell.com <><, Pseudo Engineer, itinerant idiot
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.