Issue 12332 - Zoomtext can't track the text cursor correctly
Summary: Zoomtext can't track the text cursor correctly
Status: CLOSED FIXED
Alias: None
Product: ui
Classification: Code
Component: code (show other issues)
Version: 644
Hardware: All Windows XP
: P3 Trivial (vote)
Target Milestone: OOo 1.1 Beta2
Assignee: nospam4obr
QA Contact: issues@sw
URL:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2003-03-14 11:53 UTC by nospam4obr
Modified: 2003-05-12 10:04 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description nospam4obr 2003-03-14 11:53:46 UTC 
Zoomtext 7.11 seems to be unable to track the text cursor correctly. Especially
when inserting new paragraphs by pressing return (with zoom factor of 3x),
Zoomtext sometimes moves into the wrong direction.
Comment 1 bascan 2003-03-23 19:13:54 UTC 
While editing documents in Writer, ZX 7.11 doesn't track the cursor at
all. But when the cursor is outside the magnified area and the
left-arrow button is pressed, then the magnified area suddenly jumps
to the cursor.
Comment 2 nospam4obr 2003-04-02 12:37:25 UTC 
It seems we have two issues here:

1.In the UAA, the index "length" is not a valid index for
XAccessibleText.getCharacterBounds(). Unfortunatly the index always
equals length while typing, so we should change the API in this
perspective.

2.When pressing "Enter" while the caret is at index 0 of a line, a new
paragraph gets inserted _before_ this paragraph and the actual
paragraph changes its bounding rectangle. This seems not to be honored
by Zoomtext right now. Even worse, it seems to jump to the location of
the newly inserted paragraph instead of sticking with the currently
active one. We will have to discuss this with the people from Zoomtext.
Comment 3 nospam4obr 2003-04-04 08:34:15 UTC 
Submitted a new issue (13025) for problem #2.

Andre, please change the XAccessibleText.getCharacterBounds() API so
that the "length" becomes a valid index. The implementation(s) must be
changed afterwards in the same CWS.
Comment 4 groucho266 2003-04-04 14:42:49 UTC 
I made the requested modification:  length is now a valid index.  The
associated bounding box has to have non-empty dimesions but is
otherwise left to the imagination of the implementor.
Comment 5 nospam4obr 2003-04-07 09:54:55 UTC 
Henning, could you please ensure that writer returns a non empty
rectangle for XAccessibleText.getCharacterBounds( lenght ).

CWS is UAA02.
Comment 6 nospam4obr 2003-04-07 09:59:11 UTC 
Sorry, assigned to wrong person :(
Comment 7 openoffice 2003-04-08 08:36:48 UTC 
sw/source/core/access/accpara.cxx, 
SwAccessibleParagraph::getCharacterBounds:

GetCharRect also accepts position at end of text
Comment 8 openoffice 2003-04-11 13:54:53 UTC 
fixed in uaa02: sw/source/core/access/accpara.cxx: 1.48.10.1
Comment 9 openoffice 2003-04-24 12:40:15 UTC 
Ready for QA.
Comment 10 eric.savary 2003-04-24 13:13:10 UTC 
The problem described in this issue is still there (no tracking on
return). I assume it is now a ZoomText bug which should be reassigned
accordingly and reset to "NEW". What do you think?
Comment 11 nospam4obr 2003-04-24 14:00:30 UTC 
Erik, for the "return" problem I have submitted the issue 13025 already.
Comment 12 nospam4obr 2003-04-24 14:01:08 UTC 
Verified.
Comment 13 nospam4obr 2003-05-12 10:04:31 UTC 
I have verified in the build m13s2 that the fix for this issue has
been successfully integrated.

Due to our current task handling I have to close this bug before
OpenOffice 1.1 beta2 can be released.