I think I found what the problem is but I'm not sure if it is a bug, feature 
or my mistake.
The SVG looks like:

<svg xmlns="http://www.w3.org/2000/svg"; xmlns:myns="........">
 <defs>
  <symbol id="ASYMBOL">
   <g>
    <rect width="100" height="62.5" ry="5" x="+3" y="+3" />
    <rect id="EVENT_GENERATOR" width="100" height="62.5" ry="5"/>
   </g>
  </symbol>
 </defs>
  <g id="LISTENING_NODE" myns:type="mytype" .....>
  <use xlink:href="#ASYMBOL" x="195" y="702" width="622" height="394"/>
 </g>
 .................
</svg>

When I click on the rectangle with id "EVENT_GENERATOR", the event gets 
propagated to rect[id="EVENT_GENERATOR"]/g/symbol[id="ASYMBOL"]/defs/svg 
rather than 
rect[id="EVENT_GENERATOR"]/g/symbol[id="ASYMBOL"]/g[id="id="LISTENING_NODE"]/svg
 
so the listener never gets notified.

Is this the way is supposed to be of is it a bug?





On Tuesday 09 November 2004 16:02, Thomas DeWeese wrote:
> Alessandro Di Bella wrote:
> > You are right. Registering a  listener with the root node, it gets all
> > the fired events so at some points they get intercpeted.
> >
> > if for  'pointer-events'  you mean standard swing mouse events, I guess
> > that the standard mouse interactors (zoom, apn, etc.) would be listeing
> > for them.
>
>     No, there is a CSS property called 'pointer-events' that allows you
> to adjust what geometry can generate events (see the SVG
> specification for more details).
>
> > Any idea on how to find out where the problem is? I'm not too proficient
> > in client side programming :-(
>
>     You can look at the 'target' of the event.  This is the element
> that 'initiated' the event.  I would print this out and try to
> figure out what element it is in the document (it can be
> helpful to print the parent tree and id's if they have them).
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to