Skip to content
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

[composer] add option to disable antialiasing when exporting compositions #17893

Closed
qgib opened this issue Jan 1, 2014 · 11 comments
Closed

[composer] add option to disable antialiasing when exporting compositions #17893

qgib opened this issue Jan 1, 2014 · 11 comments
Labels
Feature Request High Priority Print Layouts Related to QGIS Print Layouts, Atlas or Reporting frameworks

Comments

@qgib
Copy link
Contributor

qgib commented Jan 1, 2014

Author Name: Giovanni Manghi (@gioman)
Original Redmine Issue: 9281

Redmine category:map_composer/printing


To be more precise, it seems that when printing the option is set always as active, no matter if printing as raster or not.

@qgib
Copy link
Contributor Author

qgib commented Jan 5, 2014

Author Name: Jürgen Fischer (@jef-n)


  • subject was changed from The option "make lines apperar less jagged at the expense of some drawing performance" does not seems to be applied in the print composer to The option "make lines appear less jagged at the expense of some drawing performance" does not seems to be applied in the print composer

@qgib
Copy link
Contributor Author

qgib commented Feb 7, 2014

Author Name: Nyall Dawson (@nyalldawson)


I don't think this is a bug - to me it's a feature. Why would you want to disable anti-aliasing when exporting a composition?


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Feb 9, 2014

Author Name: aperi2007 - (aperi2007 -)


The antialiasing if no good for the black-white TIFF4 images.

In the tiff4 the main goal is have always only two color black/white.
The antialiasing work substituting some white pixel with a grey light color.
This break the possibility to have a tiff4 image.

As a use case:
the composer will allow the opportunity to export a map as a tiff georef.

But if the goal is to export a tiff4 black/white image.
The acutal setting of composer to deny the correct black/white will deny to have a set of tiff4 images georef as exportation from qgis.

@qgib
Copy link
Contributor Author

qgib commented Feb 9, 2014

Author Name: aperi2007 - (aperi2007 -)


So it is definitively a bug because It donnot reproduce exactly what there is in the canvas.

The goal of composer is produce a print of what there is on canvas .
A composer that da another think differente from canvas is not a print in qgis, but a different program.
In the canvas there is a black/white image because I can put the white transparent and having a result when export.
In composer when export I have a raster not black/white.

So I guess it is a bug.

@qgib
Copy link
Contributor Author

qgib commented Feb 9, 2014

Author Name: Nyall Dawson (@nyalldawson)


OK, that's a good point. However I don't think the existing option for antialiasing in settings is the correct solution. For one, this option is worded in a way that makes it sound like its purely for performance. I'd imagine the given how its worded the current use case is that people are disabling antialiasing in settings to speed up working with the canvas , not to change how maps are exported.
Secondly, this current setting has no effect on other composer controls such as labels, etc.
I think your use case could be better addressed by an option in the composition settings for disabling antialiasing for the whole composition. This option would be per composition, not a global setting.


  • category_id was changed from 33 to Map Composer/Printing
  • tracker_id was changed from 1 to 2
  • subject was changed from The option "make lines appear less jagged at the expense of some drawing performance" does not seems to be applied in the print composer to [composer] add option to disable antialiasing when exporting compositions

@qgib
Copy link
Contributor Author

qgib commented Feb 9, 2014

Author Name: Paolo Cavallini (@pcav)


Sounds reasonable. Nevertheless, I think this option should be added, as without it the user case described is seriously hindered. As it solves a real user issue, quite important in massive production, and it should not impact other code, I would ask to reconsider adding it to the upcoming version.


  • priority_id was changed from Normal to High
  • fixed_version_id was changed from Future Release - High Priority to Version 2.2

@qgib
Copy link
Contributor Author

qgib commented Jun 20, 2014

Author Name: Giovanni Manghi (@gioman)


  • fixed_version_id was changed from Version 2.2 to Version 2.4
  • status_id was changed from Feedback to Open

@qgib
Copy link
Contributor Author

qgib commented Jun 28, 2014

Author Name: Jürgen Fischer (@jef-n)


  • fixed_version_id was changed from Version 2.4 to Future Release - High Priority

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • easy_fix was configured as 0

@qgib
Copy link
Contributor Author

qgib commented Dec 17, 2017

Author Name: Nyall Dawson (@nyalldawson)


Applied in changeset 2f0969e.


  • status_id was changed from Open to Closed
  • done_ratio was changed from 0 to 100

@qgib qgib closed this as completed Dec 17, 2017
@qgib
Copy link
Contributor Author

qgib commented Feb 22, 2018

Author Name: Giovanni Manghi (@gioman)


  • resolution was changed from to fixed/implemented

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request High Priority Print Layouts Related to QGIS Print Layouts, Atlas or Reporting frameworks
Projects
None yet
Development

No branches or pull requests

1 participant