-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Comments
Author Name: Thaddeus - (Thaddeus -)
|
Author Name: Thaddeus - (Thaddeus -)
|
Author Name: Thaddeus - (Thaddeus -)
|
Author Name: Thaddeus - (Thaddeus -)
|
Author Name: Nathan Woodrow (@NathanW2) Attached is a patch that fixes the problem.
|
Author Name: Nathan Woodrow (@NathanW2)
|
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.
|
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:
Open test data "ComposerLockLayerForgetfulness.qgs" and I get what I see on 0001.png.
Turn off all layers but one (see 0002.png).
Open "Composer 1" and refresh view if desired.
Add raster layer -- say included "google-roadmap-z0-2-13092011_172245.png" -- and I get what is shown on 0004.png.
The text was updated successfully, but these errors were encountered: