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

Composer forgets on/off status of layers ("Lock layers for map item" feature) #14222

Closed
qgib opened this issue Sep 14, 2011 · 7 comments
Closed
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!
Milestone

Comments

@qgib
Copy link
Contributor

qgib commented Sep 14, 2011

Author Name: Thaddeus - (Thaddeus -)
Original Redmine Issue: 4283

Assignee: Marco Hugentobler


Composer is one nifty features of QGIS: on my last project I had 238 layers and 21 composer pages, I had to redo the locked layer selection many, many, ... many times.

After playing with this (QGIS 1.6 and 1.7) I discovered that adding and removing layers is what triggers the Composer lock-layer amnesia, but it actually resets all Composers lock-layer values to what the main canvas has at the time of doing the add/remove layer operation.

To reproduce:

  1. Open test data "ComposerLockLayerForgetfulness.qgs" and I get what I see on 0001.png.

  2. Turn off all layers but one (see 0002.png).

  3. Open "Composer 1" and refresh view if desired.

  4. Add raster layer -- say included "google-roadmap-z0-2-13092011_172245.png" -- and I get what is shown on 0004.png.


@qgib
Copy link
Contributor Author

qgib commented Sep 14, 2011

Author Name: Thaddeus - (Thaddeus -)


  • 3424 was configured as 0001.png

@qgib
Copy link
Contributor Author

qgib commented Sep 14, 2011

Author Name: Thaddeus - (Thaddeus -)


  • 3425 was configured as 0002.png

@qgib
Copy link
Contributor Author

qgib commented Sep 14, 2011

Author Name: Thaddeus - (Thaddeus -)


  • 3426 was configured as 0003.png

@qgib
Copy link
Contributor Author

qgib commented Sep 14, 2011

Author Name: Thaddeus - (Thaddeus -)


  • 3427 was configured as 0004.png

@qgib
Copy link
Contributor Author

qgib commented Sep 14, 2011

Author Name: Nathan Woodrow (@NathanW2)


Attached is a patch that fixes the problem.


  • category_id was configured as 33
  • pull_request_patch_supplied was changed from 0 to 1
  • fixed_version_id was configured as Version 1.7.1
  • 3428 was configured as fix_4283.patch

@qgib
Copy link
Contributor Author

qgib commented Sep 15, 2011

Author Name: Nathan Woodrow (@NathanW2)


  • assigned_to_id was configured as Marco Hugentobler
  • done_ratio was changed from 0 to 50

@qgib
Copy link
Contributor Author

qgib commented Sep 18, 2011

Author Name: Marco Hugentobler (@mhugent)


The composermap regularly checks for removed layers. The problem was that it didn't consider the non-visible layers if the layer-lock option was enabled and assumed those layers where deleted.
Fixed now in commit 820469f.


  • done_ratio was changed from 50 to 100
  • 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.7.1 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