-
-
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
wrong size of item in print composer legend when high values of map unit are used #19348
Comments
Author Name: matteo ghetta (@ghtmtt) IMHO another aspect more then a duplicate |
Author Name: Gilles Turgeon (Gilles Turgeon) I have the same problem. Here my project. It's seem that the composer dont take map units or scale in consideration when drawing the legend. |
Author Name: Gilles Turgeon (Gilles Turgeon) Sorry, forget to include project in the last message.
|
Author Name: Martin Dobias (@wonder-sk) The fix for the problem is in legend-refactoring-part2 branch:
|
Author Name: aperi2007 - (aperi2007 -) I test the patch, retrieving the qgis from wonder repo and compiling it on a debian machine. The composer still show the legend too huge, due to the mapunit setting. Opening it is , I see still a too huge symbols. A. |
Author Name: Martin Dobias (@wonder-sk) Symbols in the "prova" project are huge if the legend is not connected to any composer map (because then it is assumed that 1 map unit = 1 mm). Create a map item and associate legend item with it - the legend will show the symbols with the same size as in the map. |
Author Name: Martin Dobias (@wonder-sk) Fixed in changeset "d994e0a1b31a38ed1a82628ac913d74624ceba79".
|
Author Name: matteo ghetta (@ghtmtt)
Original Redmine Issue: 11006
Affected QGIS version: 2.4.0
Redmine category:map_composer/printing
The legend in the print composer is over-sized when high values (in map unit) are used in styling a layer.
In attach a project with a point layer, categorization style used with 200 as map unit value and the related print layout with the wrong legend size.
The text was updated successfully, but these errors were encountered: