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

Choosing Move Item Content in the print composer override Lock Layers #12109

Closed
qgib opened this issue Nov 5, 2009 · 1 comment
Closed

Choosing Move Item Content in the print composer override Lock Layers #12109

qgib opened this issue Nov 5, 2009 · 1 comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!
Milestone

Comments

@qgib
Copy link
Contributor

qgib commented Nov 5, 2009

Author Name: Luca Casagrande (Luca Casagrande)
Original Redmine Issue: 2049

Assignee: Marco Hugentobler


Hello folks:

** Add the vector data attached to the ticket
** Choose Unique Value Style
** Create a new printer composer instance, add the map and set Lock Layers On
** Back to Qgis and change the style of the layer to anything and add it to the print composer
** Qgis is fine and the two maps have got different style
** From the composer toolbar choose "Move Item Content" and click on the first map (the one with the Lock On)
** After moving the map the style change as the Lock is Off.


@qgib
Copy link
Contributor Author

qgib commented Dec 9, 2009

Author Name: Marco Hugentobler (@mhugent)


This is intended. 'Lock layers' means only to lock the layers displayed in a composer map, not their appearance.

Common use-case is this: you have 10 layers, but like to only display 2 of them in an overview map. So you set the 2 layers visible, add a composer map (as overview), select 'lock layers'. Then you go back to main map, set all 10 visible and add a second composer map in composer. Like that, you can have 2 composer maps displaying different layer sets (not layer styles).


  • resolution was changed from to wontfix
  • status_id was changed from Open to Closed

@qgib qgib added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label May 24, 2019
@qgib qgib added this to the Version 1.4.0 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
Bug Either a bug report, or a bug fix. Let's hope for the latter!
Projects
None yet
Development

No branches or pull requests

1 participant