#590 closed bug (fixed)
labels in map composer located wrong and printed bad
Reported by: | Owned by: | nobody | |
---|---|---|---|
Priority: | major: does not work as expected | Milestone: | |
Component: | Printing | Version: | Trunk |
Keywords: | Cc: | ||
Must Fix for Release: | Yes | Platform: | All |
Platform Version: | Awaiting user input: | no |
Description
SVN 6540, QT 4.2.2
As the title reads. See the linked screendumps.
that's how the project looks, and how I'd like it to be printed: http://kufaya.googlepages.com/project.png
that's how it looks in the composer: http://kufaya.googlepages.com/composer.png
Pay attention to labels 3, 13, 14 especially - although in QGIS project they are located *within* the polygons, in the map composer they are overlapping polygon's edges.
and that's what you get after printing: http://kufaya.googlepages.com/print_to_raster.png
Label 13 moved from far right to close left, labels are huge (that's maybe related to bug #548), there is a noise around each label instead of the 1 pixel buffor as I specified in the label properties. BTW, please also look at the the way the polygon's fill patterns are rendered - bug #454.
Maciek
Change History (7)
comment:1 by , 17 years ago
Milestone: | Version 0.8.1 → Version 0.8.2 |
---|---|
Version: | HEAD → 0.8 |
comment:2 by , 17 years ago
Awaiting user input: | unset |
---|---|
Version: | 0.8 → HEAD |
I think the trouble is causes by some scaling factor the original print composer dev was forced to use because of a qt3 bug. Now with qt4 the scaling should no longer be necessary, and it is probably causing the problem. I do not think it should be too hard to fix it, and it would greatly improve the usability of qgis.
comment:4 by , 16 years ago
A bug is present also in the rappresentation of the label buffers (buffer multiplied) in the printed image
comment:5 by , 16 years ago
Platform: | Debian → All |
---|---|
Platform Version: | Ubuntu Dapper |
comment:6 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I think this is fixed with recent changes. Please reopen this bug if you think it's not.
Marco
Moved to milestone 0.8.2 since we wont be fixing any further issues before the 0.8.1 release