Opened 13 years ago
Last modified 13 years ago
#3856 new enhancement
Print composer extents do not take into account CRS
Reported by: | Alister | Owned by: | nobody |
---|---|---|---|
Priority: | minor: annoyance | Milestone: | Version 1.7.0 |
Component: | Printing | Version: | Trunk |
Keywords: | Cc: | ||
Must Fix for Release: | No | Platform: | All |
Platform Version: | Awaiting user input: | no |
Description
Try this:
- enable on-the-fly reprojection
- add some layers
- create a new composer layout and add a map to it.
- make sure the extents of the composer layout are such that the layers are visible
- change the project CRS
The layers will no longer be visible in the composer layout because the composer layout extents are applied using the project CRS, and are not adjusted when the project CRS changes.
Also see #3243 which is a similar issue for spatial bookmarks.
Change History (2)
comment:1 by , 13 years ago
Priority: | major: does not work as expected → minor: annoyance |
---|---|
Type: | bug → enhancement |
comment:2 by , 13 years ago
its extent is independent from the main map extent
But if the extent is independent from the main map extent then no user would expect it to suddenly show a different part of the world if the CRS of the main map changes ;)
Note:
See TracTickets
for help on using tickets.
I don't see this as a bug. The composermap always shows the map projection and its extent is independant from the main map extent (except if you press 'set to map canvas extent' to synchronise both). A possible enhancement would be to add the possibility to have the content of a composermap in a different CRS than the main map.