> Why is the event handler being called twice sometimes?
Probably because you're doing something wrong. How can we know?
--
Marcelo - http://maps.forum.nu
--
I'll do it instead. How can we know why this is the case? We don't
know anything about your implementation, which is why the posting
guidelines (you did read them? Perhaps not) ask for a link rather than
a listing or a description.
It's FAR easier to see what's going on with a link, because something
like Firebug allows break points to be set and variables to be
examined. That's very difficult to do with a listing, and impossible
with a description.
You've described the problem: now please supply a demonstrator which
can be debugged.
On Nov 26, 6:02 pm, AF <afils...@serif.com> wrote:
> Any ideas why this is the case? ( Marcelo if you dont have any helpful
> comments dont waste your time and my time replying )
I have an additional wish:
Please do not complain about wasting your time because posts like
yours forces a complete staff of voluntary helpers to waste their
time. (I assume that no one of the helpers is a clairvoyant.)
Always pleased to be of service.
http://catb.org/~esr/faqs/smart-questions.html#not_losing (in fact all
of that is well worth reading)
I suppose that 14,000 replies from Andrew, Pil and myself combined, in
the V2 and V3 groups over the past 6 years, are just "noise". Wow!
Noisy groups! ;-)
Regards Davie
Clear description of the problem, but unsolveable without a link.
But given a link, solved in one hit; not even by brilliance just a
second-pair-of-eyes.
--
You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group.
To post to this group, send email to google-map...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
OK... I don't remember anyone reporting a similar issue. Presumably
you've searched the group and not found anything, which is why you
posted.
You asked, "Why is the event handler being called twice sometimes?"
It's entirely possible that you have found a bug in the marker
manager; it's also possible that you have made a mistake in your code.
Or, something in your code is triggering behaviour which can be
avoided by doing it differently. There's not really any way of
determining which of those possibilities obtains, given only a
description.
The issue we have in trying to help is that you have added an event
handler into the standard Google module (if I understand your
description correctly) which means that it's no longer what Google
wrote. And if we felt strongly enough to follow your example and
expend time and energy adding such a handler ourselves, hosting it and
trying it out, there's no guarantee that we will do what you did.
Perhaps you could post the issue and its resolution on the relevant
issues list:
http://code.google.com/p/google-maps-utility-library-v3/issues/list
(so it gets fixed)
-- Larry
> Its a shame that the people who felt the need to (
> unnecessarily ) reply to this post with guff have been have been such a
> distraction from solving the problem, still you live and learn, I wont be
> using the forum again to post problems or more importantly solutions. Bye
> bye.
>
> PS: If you feel the need to reply to a question without having the answer
> in the future take a deep breath, have a read from the link below, and
> think am I being constructive?
>
> *http://catb.org/~esr/faqs/smart-questions.html#not_losing*<http://catb.org/~esr/faqs/smart-questions.html#not_losing>
Regards Davie
On Nov 27, 1:34 pm, "geocode...@gmail.com" <geocode...@gmail.com>
wrote: