Feature request #13262
world file should better handle multipage composers
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Map Composer/Printing | ||
| Pull Request or Patch supplied: | No | Resolution: | |
| Easy fix?: | No | Copied to github as #: | 21323 |
Description
Hi,
While exporting a print composer to image, a world file associated to a composerMap placed on a page other than the first is currently useless. This can puzzle the user (as doc says nothing about this limitation). Since #6985 offers the user an option to choose for which composerMap a world file should be created, I think the world file should take into account the page/position of the composerMap (in case of multipage composer).
And the world file name should be the same as the exported page containing the related composerMap.
Associated revisions
[composer] Fix generation of world file when map is not on first page
fix #13262
[composer] Fix generation of world file when map is not on first page
fix #13262
(cherry-picked from d897624)
History
#1
Updated by Nyall Dawson over 8 years ago
- Status changed from Open to Closed
Fixed in changeset d8976247047397af31e27e4427c54d9a6892be03.