Opened 15 years ago

Closed 11 years ago

#833 closed defect (fixed)

Runtime map is missing legend information, if layer is initially hidden from the legend

Reported by: ksgeograf Owned by: jng
Priority: medium Milestone: 2.6
Component: Resource Service Version: 2.1.0
Severity: trivial Keywords: haspatch
Cc: tomfukushima External ID:

Description

If the layer is not visible in the legend at startup, the legend labels are not persisted into the runtime map.

Presumably, this is an attempt to optimize the size of the runtime map. However, it is possible to show the layer in the legend by toggling the corresponding flag. This will show the layer in the legend, but it will not have the legend label.

It is fairly difficult to itterate the MapDefinition and assign the missing values manually, so I propose that the optimization is removed. The resulting overhead should be minimal, and the user may enter use a blank legend label, to achieve the previous behavior.

The attached patch should work on the current trunk.

Attachments (1)

Patch for not removing legend information.diff (2.8 KB ) - added by ksgeograf 15 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 by jbirch, 15 years ago

Cc: tomfukushima added

Has this been applied?

comment:2 by tomfukushima, 15 years ago

Owner: set to chrisclaydon

comment:3 by jbirch, 14 years ago

I believe this may be a duplicate (sure looks familiar). Is this still a problem with 2.1? If so, could we get a review of the suggested fix?

comment:5 by tomfukushima, 14 years ago

Owner: changed from chrisclaydon to liuar

Reassigning to Arthur.

comment:6 by zspitzer, 13 years ago

Keywords: haspatch added

comment:7 by jng, 11 years ago

Milestone: 2.5

comment:8 by jng, 11 years ago

Milestone: 2.52.6

comment:9 by jng, 11 years ago

Owner: changed from liuar to jng

Taking ownership of the ticket. This is a problem for some applications where we want to have layers hidden first, but to reveal them later on.

comment:10 by jng, 11 years ago

Resolution: fixed
Status: newclosed

Fixed trunk (r7713, r7714), 2.5 (r7715) and 2.4 (r7716)

Note: See TracTickets for help on using tickets.