Feature request #13262

world file should better handle multipage composers

Added by Harrissou Santanna over 1 year ago. Updated over 1 year ago.

Status:Closed Start Date:08/25/2015
Priority:Normal Due date:
Assigned to:- % Done:

0%

Category:Map Composer / Printing
Target version:Future Release - Nice to have
Platform: Resolution:
Platform version: Pull Request or Patch supplied:No
Status info: Tag:

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

Revision d8976247047397af31e27e4427c54d9a6892be03
Added by Nyall Dawson over 1 year ago

[composer] Fix generation of world file when map is not on first page

fix #13262

Revision 8538be61351f94a10d9d03f9838e8507f2359c53
Added by Nyall Dawson over 1 year ago

[composer] Fix generation of world file when map is not on first page

fix #13262

(cherry-picked from d897624)

History

Updated by Nyall Dawson over 1 year ago

  • Status changed from Open to Closed

Also available in: Atom