This is sadly a leaky abstraction that is unavoidable at the moment.
You have to be cognizant of the fact that although you're writing .net code,
it is .net code that ultimately wraps and interops to native C/C++ code, so
its memory management and lifecycle issues can crop up in your .net code
I thought about this some more.
Since your aim is to ultimately be showing some kind of URL the task pane
(or new window, or frame) in response to a selection, and my aim is for this
viewer to be as much configuration-driven as it possibly can be (I want
custom coding to be a last resort solution
Thanks for the link, it makes it more clear what you're trying to achieve.
I think the easiest thing is for me to add a new viewer API to register a
handler for selection changes. It will be at the same level as other AJAX
viewer APIs, so you can get to it from the task pane content through
That sound's great.
I think, this is a good solution.
Thank you in advanced.
Matze
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/react-layout-Hooking-to-events-in-the-AJAX-viewer-OnSelectionChanged-tp5309934p5310235.html
Sent from the MapGuide Users mailing list
I do believe you are leaking 1 MgByteReader per call.
Here is the definition of the function call:
public virtual *MgByteReader* CreateRuntimeMap(MgResourceIdentifier
mapDefinition, string sessionId, int requestedFeatures, int
iconsPerScaleRange);
It returns a MgByteReader. I strongly recommend
