Issue 55981 - off by 0,5 error in getIndexAtPoint()
Summary: off by 0,5 error in getIndexAtPoint()
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: 680m131
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: eric.savary
QA Contact: issues@sw
URL:
Keywords: accessibility
Depends on:
Blocks: 90510
  Show dependency tree
 
Reported: 2005-10-14 09:45 UTC by nospam4obr
Modified: 2013-08-07 14:43 UTC (History)
2 users (show)

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

Attachments
sample document with formatting (5.88 KB, application/vnd.oasis.opendocument.text)
2006-09-01 13:48 UTC, nospam4obr 		no flags Details
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 2005-10-14 09:45:27 UTC 
The implementation of XAccessibleText.getIndexAtPoint() returns already the next
character when given a point in the right half of a character.
Comment 1 nospam4obr 2005-10-14 09:46:20 UTC 
Adding keyword accessibility
Comment 2 thomas.lange 2006-06-20 14:25:43 UTC 
.
Comment 3 Mathias_Bauer 2006-07-10 10:51:01 UTC 
changing target
Comment 4 thomas.lange 2006-07-12 09:32:13 UTC 
Using the Java Access Bridge 2.0 (and the JavaFerret from that same version) and
testing with 680m145 and 680m175 the bug seems to have disappeared meanwhile.

TL->ES: Please check as well. Thanks!
Comment 5 eric.savary 2006-08-21 15:39:38 UTC 
ES->OBR: please verify. Thank you!
Comment 6 nospam4obr 2006-09-01 13:48:24 UTC 
Created attachment 38890 [details]
sample document with formatting
Comment 7 nospam4obr 2006-09-01 13:54:02 UTC 
Actually it turns out not to happen with text without character attributes. I
can still reproduce the problem with the attached document using JavaFerret's
"Update Settings - update with F1 (mouse point)" functionality.
Comment 8 thomas.lange 2006-09-25 15:41:49 UTC 
It seems this problem occurs only if the text portion at question is exact 1
character long.
Since this is a rather unusual size this should not be a OOo 2.1 issue, it
should be retargeted to OOo later.
Comment 9 nospam4obr 2006-09-26 09:03:31 UTC 
I have no idea whether there are languages where having text attributes for a
one character word do make sense. 

I agree that the special circumstances the problem appear make a fix for it less
urgent, but accessibility issues should never have OOo Later target => 2.x.
Comment 10 thomas.lange 2006-09-26 09:57:04 UTC 
TL->FME: Please take over. Thanks!
Comment 11 thomas.lange 2006-09-26 09:57:18 UTC 
.
Comment 12 Mathias_Bauer 2007-12-04 13:30:30 UTC 
target 3.0
Comment 13 frank.meies 2008-03-19 14:45:07 UTC 
Fixed in cws sw300bf02, accpara.cxx
Comment 14 frank.meies 2008-03-21 16:34:11 UTC 
fme->es: Ready for QA.
Comment 15 eric.savary 2008-04-02 11:42:14 UTC 
Verified
Comment 16 thorsten.ziehm 2009-07-20 15:54:55 UTC 
This issue is closed automatically and wasn't rechecked in a current version of
OOo. The fixed issue should be integrated in OOo since more than half a year. If
you think this issue isn't fixed in a current version (OOo 3.1), please reopen
it and change the field 'Target Milestone' accordingly.

If you want to download a current version of OOo =>
http://download.openoffice.org/index.html
If you want to know more about the handling of fixed/verified issues =>
http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues