on the mouseOver issue - i can't tell why it's happening, but I can 
tell you what is happening...

i loaded a map - rolled the mouse around, and after a few mouseOvers 
there was some overs that wouldn't show, but these seemed to be 
repeatable

so I really zoomed in

at this point I noticed that the lines allso have different mouseOver 
function

rolling quickly from one polygon, over path, onto the next polygon 
seems to create the condition 

    first polygone - mouseOver - changes state - fill grey
                   - MouseOut - changes state - fill defualt
    line           - mouseOver - change state - stroke blue
                   - mouseOut - change state - stoke default
    next polyGon   - mouseOver - failed

rolling mouse slowly doesn't fail the mousOver

this suggest it is an instruction set problem, and that the viewers 
you are using cannot handle the focus change so quickly

i have no idea how you might change this... just letting you know 
what I saw





--- In [email protected], Bart <[EMAIL PROTECTED]> wrote:
> (cross-posted because of question overlap)
> 
> Hey all,
> 
> 
> I'm building a map interface and the mouseover
> events don't seem to trigger like I think they should. 
> 
> I essentially have three data types, namely 
> points, lines and areas, which are:
>   circle (fill only, stroke:none, pointer-events: visibleFill), 
>   line (stroke only, fill:none, pointer-events: visibleStroke) and 
>   area (fill only, stroke:none, pointer-events: visibleFill) 
> elements in SVG (the CSS set via classes).
> 
> 
> However, it seems to regularly decide to
> not react or decide a part of an area isn't part of
> it in terms of mouseover. 
> 
> `It' being ASV3 and Batik (I havent tested on
> more), which seem to do do the same thing,
> so it may be because of data,  although the
> viewers seems to differ a little in what areas
> they react to, and it may be my delusion but
> it also seems to vary with zoom level even
> when zooming is just viewBox alteration.
> 
> 
> Possibly related is the fact that the help button
> seems to sometimes stop working. Event overload,
> perhaps?
> 
> 
> The SVG is at:
> http://svg.scarfboy.com/newiface/test.svg
> (I may be working on it and break it)
> 
> The simplest example layer would be 'quads':
> the left area only responds to part of it,
> apparently only on the right (and bottom)
> sides of it.  
> 
> 
> 
> Another question: most of it seems to work in
> Batik, except dragging (which I disabled and
> reimplemented), which makes squiggle
> stop drawing. Any idea what could cause
> it to react like that?
> 
> 
> Greet,
> --Bart




-----
To unsubscribe send a message to: [EMAIL PROTECTED]
-or-
visit http://groups.yahoo.com/group/svg-developers and click "edit my 
membership"
---- 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/svg-developers/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to