Feature selection only works on top layer - Often not appropriate

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Add multiple layers to the AtlasMapper
2. Perform a feature request by clicking on the map
3. Only the top most layer will get the feature request.

What is the expected output? What do you see instead?
Quite often the top most layer is labelling or hillshading which is does not 
produce useful feature request. Potentially we could disable the feature 
request for these layers in the manual override, but this is not always the 
solution. With the current implementation it is not possible to
compare values from different layers at the same location. 

The client should display the feature request to the layers in different tabs 
perhaps.

Original issue reported on code.google.com by eric.law...@gmail.com on 26 Apr 2012 at 2:37

[GoogleCodeExporter]

New "feature request".

The window show one "feature request" response, with a drop down to allow the 
user to switch to a different layer.

Algo:
The window display a dropdown (in place of the layer title), containing all 
layers that has return a response. When the user select a layer from that list, 
the response from that layer is shown and the layer become the "layer of 
interest". If an other "feature request" is sent, the "feature request" window 
automatically switch to the "layer of interest" as soon as it receive a 
response for that layer. Otherwise, the top most layer is shown.

This solution fix the most annoying problems with feature requests, but it's 
still not very touch device friendly.

Original comment by lafond.g...@gmail.com on 23 Dec 2013 at 8:18

• Changed state: Started
• Added labels: Milestone-NextRelease

[GoogleCodeExporter]

Fixed in 1.4.8

Original comment by lafond.g...@gmail.com on 24 Dec 2013 at 1:12

• Changed state: Fixed
• Added labels: IssueClosed-1.4.8