07-19-2018 02:14 AM
is it wanted that only one layer can be set active in desktop application?
I'd like to understand why?
If I could set more layers active I also could consume more tooltips for example.
Thanks in advance
Solved! Go to Solution.
07-23-2018 04:44 AM
It is true that a single layer is able to be active in Desktop M.App currently.
It is also true that this limits tooltips being available for non active layers. In this way I suggest adding this idea to the Product Ideation page for additional comments/consideration.
07-25-2018 02:11 PM
it WAD: the active layer is used to select properties from the database and issue queries to that layer only.
with the selection tools you can select features from active layer (if any) or you get the list of layers you would like to select from (then this layer becomes active). Starting from the selection you may run an associated predefined query to get attribute values.
07-31-2018 12:03 AM
thank you both for your replies!
To go a little further:
We are planning to roll out desktop client as standard webclient to our customers, so we are investigating which method fits best to get information about objects in the map.
As far as I see I have follwing options:
Is it possible, to use sth. like an "advanced tooltip" in MAE? I think there is similar function in German "Kommunal" extension for GMSC.
There I am able to start with the selection tools and get a predefined info about every locatable object in a separate area/window embedded in the app - independant if they are all on the same layer or not.
If I understood you right, Stefano - I am able to select features from an active layer and run a predefined query - do you mean a workflow? I f you are talbing about a simple rich client sql query, must this query have a special placeholder which considers the selection?
Thanks in advance!
07-31-2018 03:09 AM
you can propose the "extended tooltip" like tool in the Product Ideation board, so we can understand how common is a requirement like this.
About the queries I meant SQL queries configured in Studio. Please have a look at the training material here:
in particular Exercise 5, task 2.