GNOME Bugzilla – Bug 100944
need more efficient text APIs for screen review bounds
Last modified: 2004-12-22 21:47:04 UTC
IN order to do screen review without lots of client processing and many IPC calls, we need some more efficient API for relating bounding boxes to ranges within an AccessibleText object. At the moment we have bounds API for characters, but not ranges, so range information must be built up over many API calls. Ideally we should have: in Accessibility_Text.idl: void getRangeExtents (in long start_offset, in long end_offset, out long x, out long y, out long length, out long width, in short coordType); void getRangeFromBounds (out long start_offset, out long end_offset, in long x, in long y, in long width, in long height, in short coordType); (with corresponding API in cspi).
Created attachment 13066 [details] [review] attachment to provide the new API in IDL
Created attachment 13082 [details] [review] new attachment with improved API and also implementation.
Updated patch, including implementation. We now return a sequence of Accessibility_Text_Range structs from the getBoundedRanges() call, which is what ATs will need.
Created attachment 13083 [details] [review] completed version of patch including ChangeLog, version rev, etc.
Created attachment 13088 [details] [review] revised patch incorporating feedback from michaelm, and perf improvements for RangeExtents.
Created attachment 13092 [details] [review] this patch REVERTS the visual bell patch. (note, it's *not* a '-R' patch)
please ignore stray metacity patch attached.
the API patch has been applied.