xmlgraphics-batik-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 47099] [PATCH] Regression: cursor behavior in text elements weird after revision 761228
Date Mon, 27 Apr 2009 13:27:53 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=47099


Helder Magalhães <helder.magalhaes@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |NEW
         OS/Version|Windows Vista               |All




--- Comment #2 from Helder Magalhães <helder.magalhaes@gmail.com>  2009-04-27 06:27:44
PST ---
(In reply to comment #1)
> I can't reproduce this bug.

Weird, I still can. Just tried with an untouched fresh Batik checkout (revision
768952 ( https://svn.apache.org/viewcvs.cgi?view=rev&rev=768952 )). made a "build clean",
"build squiggle" and opened the report's URL.

Nevertheless, I forgot to mention a couple of things in the original report:
 * This was originally seen in a machine with Windows Vista SP1;
 * Java environment is Sun's JDK 1.6.0 update 13;
 * This reproduces with a Squiggle windows which is not maximized.


> It's hard for me to see how the bug described bug could be
> caused by this.  The block of code you updated is only used
> to locate tspan's within a text element.  There are no tspans
> in this example.

Maybe the anchor within the text element will make Batik internally handle that
text portion as in a tspan (but then again, I'm just guessing...)?

I was also able to reproduce using different configurations:
 * In a (different) machine with Windows XP SP3 and both Sun's JDK 1.6.0 update
13 and JDK 1.5.0 update 17;
 * In a (yet different) machine using Ubuntu 8.10 and Sun's Java 1.6 with a
Batik nightly build [1];
(This suggest towards something which affects all platforms -- I'm setting it,
even though Mac wasn't tried.)

Few more thoughts:
 * Using a windows size of 800x600 makes the issue reproducible (that is, the
unexpected pointer cursor appearing on top of the "Text Cursor" glyphs);
 * This can also be checked by placing the mouse pointer over the glyphs of
"Pointer Cursor", which should display a pointer cursor (and most times
doesn't);
 * Applying the proposed patch, "build clean", "build squiggle" and opened the
report's URL no longer reproduces the error (attempted with maximized and also
with several window sizes for sure).


> Your proposed patch will cause problems.  rev 761228 changed
> the way that block of code works so that 'pt' must already be
> in the elements local coordinate system.  So applying that
> transform again will cause trouble.

Humm... But I was still suffering from the issue without the patched code
(patching it makes the weird cursor behavior to go away, both with Java 1.5 and
Java 1.6). As I'm not able to quite understand the changes in
"StrokingTextPainter.java", the only things that also occurs to me is that some
local changes were not committed...?


I'm not sure what kind of additional information can I provide in order to help
reducing this... :-|


[1] http://arc.mcc.id.au/batik-nightly/webstart/squiggle.pl

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org


Mime
View raw message