Feature request #13262
world file should better handle multipage composers
|Pull Request or Patch supplied:||No||Resolution:|
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.