We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug It is not possible to export map configuration in context manager, only the 'export context' option is now available.
To Reproduce
Expected behavior Able to export map configuration while configuring a context
Actual behavior Since the control keys on both toggle operations are identical. Both the panel are opened and one overlapping the other
georchestra/mapstore2-georchestra#679
The text was updated successfully, but these errors were encountered:
geosolutions-it#9889: Fix - Unable to export map configuration in con…
2a5472f
…text manager
#9889: Fix - Unable to export map configuration in context manager (#…
b3ffd90
…9896) * #9889: Fix - Unable to export map configuration in context manager * Control added to constant
dfdb136
…text manager (geosolutions-it#9896) * geosolutions-it#9889: Fix - Unable to export map configuration in context manager * Control added to constant (cherry picked from commit b3ffd90)
2dcde13
…9896) (#9898) * #9889: Fix - Unable to export map configuration in context manager * Control added to constant (cherry picked from commit b3ffd90)
dsuren1
ElenaGallo
Successfully merging a pull request may close this issue.
Describe the bug
It is not possible to export map configuration in context manager, only the 'export context' option is now available.
To Reproduce
Expected behavior
Able to export map configuration while configuring a context
Actual behavior
Since the control keys on both toggle operations are identical. Both the panel are opened and one overlapping the other
Issue reference
georchestra/mapstore2-georchestra#679
The text was updated successfully, but these errors were encountered: