Commit cc7e960
1 parent f984242 commit cc7e960
1 file changed
+6
-0
lines changedLines changed: 6 additions & 0 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
5881 | 5881 |
| |
5882 | 5882 |
| |
5883 | 5883 |
| |
| 5884 | + | |
| 5885 | + | |
| 5886 | + | |
| 5887 | + | |
| 5888 | + | |
| 5889 | + | |
5884 | 5890 |
| |
5885 | 5891 |
| |
5886 | 5892 |
| |
|
5 commit comments
nirvn commentedon May 12, 2017
Doh, I forgot to add it to the commit. You are right. The force vector flag isn't necessary but the remaining ones are.
nirvn commentedon May 12, 2017
@nyalldawson , thinking about this some more, I'm wondering whether we should have the drawSelection flag on. It'd behave like 2.x's save as image, and it can be useful when someone wants to do a "quick and dirty" visual highlight.
nyalldawson commentedon May 12, 2017
Agreed. But not the editing markers. And antialiasing should respect the canvas setting for antialiasing too.
nirvn commentedon May 13, 2017
@nyalldawson , we could consider removing non-antialiasing altogether for QGIS 3.0. Is it really relevant and/or useful to do non-antialiased rendering circa 2017?
nyalldawson commentedon May 13, 2017
I understand that some people use it to export maps with a limited color palette, so i think the option should remain.