Opened 14 years ago

Last modified 14 years ago

#2738 new enhancement

Legend customizations are not saved in Composer Template

Reported by: hdus Owned by: mhugent
Priority: major: does not work as expected Milestone: Version 1.7.0
Component: Printing Version: Trunk
Keywords: Cc: marco@…
Must Fix for Release: No Platform: All
Platform Version: Awaiting user input: no

Description

  1. Create a composer legend group and add some items
  2. Save the composer map as template
  3. Reload the saved composer template
  4. The legend group does exist no longer

Change History (4)

comment:1 by jctull, 14 years ago

Cc: marco@… added
Owner: changed from nobody to mhugent
Platform: RedHatAll
Summary: Grouped Legend Items are not saved in Composer TemplateLegend customizations are not saved in Composer Template

Additionally, no information regarding customized legends is preserved when a template is loaded. Try creating a composer item, add a legend, then delete a few items. Add another with those items only. Save the template and load it in a new composer. All legend instances will be populated with every item in the map canvas.

My guess is these two items are related. Effectively, legend instances are not having any information saved other than location and font information.

I've changed the bug title from "Grouped Legend Items are not saved in Composer Template" to reflect this more general problem.

comment:2 by mhugent, 14 years ago

The legend structure is saved in the template (see content of the xml file). However, a template can be opened in a project with totally different layers and therefore is expected to not restore the saved legend content (otherwise, the legend content would be wrong if opening the template in other projects).

It would however make sense to add a test if the legend id is present in the project.

comment:3 by pcav, 14 years ago

Milestone: Version 1.5.0Version 1.6.0
Must Fix for Release: YesNo

comment:4 by mhugent, 14 years ago

Type: bugenhancement

changing to enhancement. Current behaviour is correct, but automatically trying to create a 'best fit' would be perfect.

Note: See TracTickets for help on using tickets.