You raise an interesting point about how our viewer offerings are being used.
Namely, I wasn't expecting embedding the viewer in a frame/iframe to feature
prominently as a common use case. The viewer API design thus far has been
going on the assumption that the react viewer is either the
I've made an issue to track this:
https://github.com/jumpinjackie/mapguide-react-layout/issues/144
- Jackie
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/react-layout-Hooking-to-events-in-the-AJAX-viewer-OnSelectionChanged-tp5309934p5310240.html
Sent from the MapGuide
Hi, we use nearly all fusion events (MAP_LOADED, MAP_SELECTION_ON,
MAP_SELECTION_OFF etc.) from outside (the fusion viewer is in an iframe).
Will this be possible with the new react-layout?
Thank you, svlad
--
View this message in context:
Hi,
we consume external WMS services. Sometimes these services are not available or
do not work properly. It can take some time until we (admins) actually notice
that - either by users getting back to us or through log file messages.
Now, for the user it is sometimes not noticable that a layer
Guys,
Thanks a lot for the explanation! Appears this was the problem indeed.
Now, every time the CreateMap function is executed, I capture the returned
object to a variable. Then I call Dispose() on it, and the proble is solved.
I'll make sure to check the rest of my code on similar issues.