Thanks for the explanation.Do you know where I would find the original source code for the OverViewMap widget that is part of the out-of-the-box build?
Thanks again for the uncompiled code.I was reviewing the code and I do not understand how the .mxml file knows how to retrieve the data from the .xml file.if (configXML) { overviewMap.configXML = configXML; }This seems like where the mxml file is trying to access the xml, but how does it know to look for OverviewMapWidget.xml if it is not explicitly passed in the variable configXML?
Is there any chance you can add the uncompiled code to the page where the compiled code is located?
Thank you very much GISDev01 for this useful enhancement.Is there any chance you can add the uncompiled code to the page where the compiled code is located?
Could you add the size of the widget as a configurable variable in the xml file and then send that recompiled swf file along with the xml showing the syntax for changing the size in the xml file? That would be greatly appreciated.
Thank you.Do you know how to make this a configurable variable that could be changed in the xml file so it would not need to be recomplied every time you need to change its size, possibly for different applications?
<s:BorderContainer id="viewBox" width="250" width.collapsed="{toggleIcon.width}" height="250" height.collapsed="{toggleIcon.height}" backgroundAlpha="1.0"> <esri:Map id="overviewMap" width="250" height="250"
Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.