After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 100944 - need more efficient text APIs for screen review bounds
need more efficient text APIs for screen review bounds
Status: RESOLVED FIXED
Product: at-spi
Classification: Platform
Component: api
unspecified
Other All
: Normal enhancement
: ---
Assigned To: bill.haneman
bill.haneman
Depends on:
Blocks:
 
 
Reported: 2002-12-11 13:40 UTC by bill.haneman
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Attachments
attachment to provide the new API in IDL (3.44 KB, patch)
2002-12-17 12:06 UTC, bill.haneman
none Details | Review
new attachment with improved API and also implementation. (18.40 KB, patch)
2002-12-17 21:30 UTC, bill.haneman
none Details | Review
completed version of patch including ChangeLog, version rev, etc. (21.77 KB, patch)
2002-12-17 23:50 UTC, bill.haneman
none Details | Review
revised patch incorporating feedback from michaelm, and perf improvements for RangeExtents. (22.91 KB, patch)
2002-12-18 13:24 UTC, bill.haneman
none Details | Review
this patch REVERTS the visual bell patch. (note, it's *not* a '-R' patch) (21.26 KB, patch)
2002-12-18 15:50 UTC, bill.haneman
none Details | Review

Description bill.haneman 2002-12-11 13:40:54 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).
Comment 1 bill.haneman 2002-12-17 12:06:51 UTC
Created attachment 13066 [details] [review]
attachment to provide the new API in IDL
Comment 2 bill.haneman 2002-12-17 21:30:04 UTC
Created attachment 13082 [details] [review]
new attachment with improved API and also implementation.
Comment 3 bill.haneman 2002-12-17 21:30:55 UTC
Updated patch, including implementation.
We now return a sequence of Accessibility_Text_Range structs from the
getBoundedRanges() call, which is what ATs will need.
Comment 4 bill.haneman 2002-12-17 23:50:42 UTC
Created attachment 13083 [details] [review]
completed version of patch including ChangeLog, version rev, etc.
Comment 5 bill.haneman 2002-12-18 13:24:44 UTC
Created attachment 13088 [details] [review]
revised patch incorporating feedback from michaelm, and perf improvements for RangeExtents.
Comment 6 bill.haneman 2002-12-18 15:50:55 UTC
Created attachment 13092 [details] [review]
this patch REVERTS the visual bell patch. (note, it's *not* a '-R' patch)
Comment 7 bill.haneman 2002-12-18 15:52:18 UTC
please ignore stray metacity patch attached.
Comment 8 bill.haneman 2003-01-23 16:01:23 UTC
the API patch has been applied.