Hi! Thanks Daniel for taking responsibility for this issue, which has been around for far to long :-) I agree that ticket 1952 discusses a more flexible functionality, but I don't think we need to make this more complicated than it is already. I can't see a situation where you would like to hide a layer from one service type, but not in an other (but thats my opinion). Fixing the 2582 bug would satisfy many of the user needs on this issue.
Taking the GROUP functionality into consideration seems to be important, as this possibly could cause some mixup if a hidden layer is inside a group layer. What if all layers inside a GROUP is hidden? Should the group layer still be exposed in the capabilities document? I'd say yes, but other may have a different opinion. Regards, Pål Kristensen Martin Kofahl wrote: > > Perfect! Although the solution described in ticket 1952 might be more > flexible for future use. > > Daniel Morissette wrote: >> paalkr wrote: >>> Hi all devs! >>> >>> What is the status on ticket >>> http://trac.osgeo.org/mapserver/ticket/2582 >>> 2582 ? Is this going to be included in 5.4? >>> >> >> Yes, we'll take care of it for 5.4. >> >> Daniel > _______________________________________________ > mapserver-users mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/mapserver-users > > -- View this message in context: http://n2.nabble.com/Status-on-ticket-2582--tp2337548p2341220.html Sent from the Mapserver - User mailing list archive at Nabble.com. _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
