Legend.js: startGroup Initial value is checked, wether or not set in Studio

[poulet1212]

In studio you can set a group to be "initially displayed in the map". You can set what you want, legend.js will always initially set the group as "checked".

Legend.js: Draw function

for (var i=0; i<startGroup.groups.length; i++) {
            startGroup.groups[i].visible = true;
            this.processMapGroup(startGroup.groups[i], this.oRoot);
}

The fellowing line should be removed, it should'nt be always set as "true".

startGroup.groups[i].visible = true;

[jbirch]

I'm not able to duplicate this problem using the 1.1 branch. When I change the value of whether to show the group initially in either Maestro or MG Studio, Fusion seems to honour this change.

As far as I can tell, the code change that you suggest only affects the top-most group, which is the name of the Map (e.g. Sheboygan). The other map groups are toggled in the processMapGroup method based on the value of the group's visibility.

I think that the Fusion developers will need additional information to track down the problem you are seeing, such as MapGuide version, the version of Fusion that you're using, and a package (MGP) that shows the problem.

[poulet1212]

Absolutely right, it affects only the top-most group. I was not aware of the specification, if you say the top-most group is the name of the map, sure the visibility has to be set to true. Actually, I understood that in another way, I have for top-most groups many folders like: -cadastral -transportation -etc...

Understanding what you say, I should do things like this: -my_map_name --cadastral --transportation --etc...

and then, the "problem" no longer occurs, because I can set visibility in MGStudio for subfolders. I just mistook how to do the things in the right way, I think we can close this ticket.

Rémy

[poulet1212]

Once again, the formating above is not good, sorry.

Absolutely right, it affects only the top-most group. I was not aware of the specification, if you say the top-most group is the name of the map, sure the visibility has to be set to true. Actually, I understood that in another way, I have for top-most groups many folders like:

->cadastral
->transportation
->etc... 

Understanding what you say, I should do things like this:

->my_map_name
--->cadastral
--->transportation
--->etc... 

and then, the "problem" no longer occurs, because I can set visibility in MGStudio for subfolders. I just mistook how to do the things in the right way, I think we can close this ticket.

Rémy