xmlgraphics-batik-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "chandra srinivasan" <chandrasr...@hotmail.com>
Subject Re: getTarget() vs getCurrentTarget()
Date Fri, 10 Jun 2005 21:48:42 GMT
<html><div style='background-color:'><DIV class=RTE>
<P>Hi Thomas</P>
<P>Thanks for your response. I couldn't attach the svg map since it's size is more than
100kb (the limit for&nbsp; this forum's email system). let me know How else should i send
the file. like maybe break it into two or any better ideas.</P>
<P>Chandra Srinivasan<BR><BR></P><BR><BR><BR>&gt;From:
Thomas DeWeese &lt;Thomas.DeWeese@Kodak.com&gt;<BR>&gt;Reply-To: batik-users@xmlgraphics.apache.org<BR>&gt;To:
batik-users@xmlgraphics.apache.org<BR>&gt;Subject: Re: getTarget() vs getCurrentTarget()<BR>&gt;Date:
Wed, 08 Jun 2005 07:55:49 -0400<BR>&gt;<BR>&gt;Hi Chandra,<BR>&gt;<BR>&gt;chandra
srinivasan wrote:<BR>&gt;<BR>&gt;&gt;I am using svg maps generated
by Oracle's Mapviewer product. The <BR>&gt;&gt;svg files have a displayLabel()
javascript function which calls <BR>&gt;&gt;evt.getTarget() to get the mousedover
element and displays the <BR>&gt;&gt;label text. this works fine in Internet
explorer. but not in <BR>&gt;&gt;squiggle or any app using JSVGCanvas. if I
modify the call to <BR>&gt;&gt;'getTarget()' to getCurrentTarget(). it works
fine in both IE and <BR>&gt;&gt;squiggle.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;I'd
interested in getting more information on this as I <BR>&gt;wasn't<BR>&gt;previously
aware that ASV incorrectly implemented getTarget - <BR>&gt;something<BR>&gt;that
I would most likely have encountered.&nbsp;&nbsp;Can you provide a small<BR>&gt;example
that works in ASV (what I'm presuming you are using in IE) <BR>&gt;and<BR>&gt;fails
in Batik?<BR>&gt;<BR>&gt;&gt;I don't want to be fixing the scripts
in the svg maps since there <BR>&gt;&gt;will be many of them.is there anything
I could do in my code to <BR>&gt;&gt;handle this situation.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;You
can break Batik's DOM Event's implementation, it lives in<BR>&gt;batik.dom.events.EventSupport,
I have no idea what inside Batik<BR>&gt;this might break - in my experience this
is a really bad idea.<BR>&gt;I would suggest submitting a bug report to Oracle as
this is only<BR>&gt;going to become a bigger issue for 
them as implementations like<BR>&gt;Mozilla and the various mobile vendors move
into wider circulation,<BR>&gt;they will have to conform to the spec rather than
depend on ASV <BR>&gt;bugs.<BR>&gt;<BR>&gt;<BR>&gt;---------------------------------------------------------------------<BR>&gt;To
unsubscribe, e-mail: <BR>&gt;batik-users-unsubscribe@xmlgraphics.apache.org<BR>&gt;For
additional commands, e-mail: <BR>&gt;batik-users-help@xmlgraphics.apache.org<BR>&gt;<BR></DIV></div></html>

To unsubscribe, e-mail: batik-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-users-help@xmlgraphics.apache.org

View raw message