I am configuring an application template through ArcGIS online.
The template allows you to select which tools will be included and you can specify the active tool as well.
I would like the Active Tool to be None - but even with None selected the Basemap Gallery is displayed.
I found this thread on GitHub (https://github.com/Esri/Viewer/issues/34) but the suggestion of clicking the edior/display editor toolbar did not work for me.
Any help would be appreciated.
Thanks!
Solved! Go to Solution.
Looks like a bug related to the one you linked to earlier. I have a fix for this that will be in the next release of Online. If you are able to host the template locally I could send you the fix now?
Is your app/webmap public? If so can you send the url?
Kelly,
Please see the url below
http://mississauga.maps.arcgis.com/apps/Viewer/index.html?appid=73909e939be34d2b931f0765ba3bf4a6
Thanks,
David
Thanks David,
If I look at the application values it looks like the 'activeTool' option hasn't been specified. When you configured it which tool did you set as active?
Here's the app values that show the options that have been configured.
Kelly,
The active tool is set to none, which is what I would like.
As a test I created a web map using the Esri Map Layers that are provided and selected a dataset from the Demographic and Lifestyles sub section and the "none" as the active tool worked.
Looks like a bug related to the one you linked to earlier. I have a fix for this that will be in the next release of Online. If you are able to host the template locally I could send you the fix now?
Kelly,
I am not able to host the template locally.
Do you happen to know when the next release of Online will be? I have several maps I would like to apply the new template to, but will not do so until this issue is resolved.
Thanks
The next release should be around Dev Summit - so early March.
I am experiencing the exact same behavior. The tools I have selected are find location, legend and share. With the active tool set to none, the legend appears. The editor/toolbar work around did not fix the problem.
Claire this issue should be resolved in the next release which is due out soon.