On 7/23/05, Garry Haywood <[EMAIL PROTECTED]> wrote: > > 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
Yeah, it's a possibility, it not being able to dispatch the events quick enough, perhaps some non-parallel dispatching or something strange like that. I'm looking at playing with event bubbling right now. However, that does not explain why it also does it for quads, which has a grand total of three lines, two points (circles) and two areas; it's so little data it's almot human readable, and still the left area, line and point do not react on anything big about the right fifth part of them, areawise. There almost seem to be some phantom objects blocking events. Oh, in fact, that's looks to be it. the nonresponsive area is right under the vector selectionLists (menu's) I yanked from carto.net. They probably did some silly half-invisibility thing I wasn't counting on with my pointer-events settings. That would also explain zoom having some but not much effect - since zooming moves the extent of the objects. Cool, it was driving me crazy:) Thanks, --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/
