Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Legend customizations are not saved in Composer Template #12798

Closed
qgib opened this issue May 20, 2010 · 8 comments
Closed

Legend customizations are not saved in Composer Template #12798

qgib opened this issue May 20, 2010 · 8 comments
Labels
Feature Request Print Layouts Related to QGIS Print Layouts, Atlas or Reporting frameworks

Comments

@qgib
Copy link
Contributor

qgib commented May 20, 2010

Author Name: Horst Düster (@hdus)
Original Redmine Issue: 2738

Redmine category:map_composer/printing
Assignee: Marco Hugentobler


  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
@qgib
Copy link
Contributor Author

qgib commented May 20, 2010

Author Name: John Tull (John Tull)


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.

@qgib
Copy link
Contributor Author

qgib commented Jun 7, 2010

Author Name: Marco Hugentobler (@mhugent)


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.

@qgib
Copy link
Contributor Author

qgib commented Jun 12, 2010

Author Name: Marco Hugentobler (@mhugent)


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

@qgib
Copy link
Contributor Author

qgib commented Dec 16, 2011

Author Name: Giovanni Manghi (@gioman)


  • fixed_version_id was changed from Version 1.7.0 to Version 1.7.4

@qgib
Copy link
Contributor Author

qgib commented Apr 15, 2012

Author Name: Giovanni Manghi (@gioman)


  • fixed_version_id was changed from Version 1.7.4 to Version 2.0.0

@qgib
Copy link
Contributor Author

qgib commented Oct 6, 2012

Author Name: Pirmin Kalberer (Pirmin Kalberer)


  • fixed_version_id was changed from Version 2.0.0 to Future Release - Nice to have

@qgib
Copy link
Contributor Author

qgib commented Apr 6, 2014

Author Name: Jürgen Fischer (@jef-n)


  • category_id was changed from 33 to Map Composer/Printing

@qgib
Copy link
Contributor Author

qgib commented Mar 21, 2017

Author Name: Nyall Dawson (@nyalldawson)


Fixed in changeset "616868efbeb72633fd0798efeaee05e75a92de71".


  • status_id was changed from Open to Closed

@qgib qgib added Feature Request Print Layouts Related to QGIS Print Layouts, Atlas or Reporting frameworks labels May 24, 2019
@qgib qgib added this to the Future Release - Nice to have milestone May 24, 2019
@qgib qgib closed this as completed May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Print Layouts Related to QGIS Print Layouts, Atlas or Reporting frameworks
Projects
None yet
Development

No branches or pull requests

1 participant