[prev in list] [next in list] [prev in thread] [next in thread] 

List:       qgis-developer
Subject:    [Qgis-developer] Intensive work with print composer become hard due to some bugs. Any help?
From:       DelazJ <delazj () gmail ! com>
Date:       2015-11-25 16:47:13
Message-ID: CAECJsSr6x-jG3VwkcGyTQYaghkYnhwBdHGCEPnB+97wu6hE7cQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Looking at the quick way FTools bugs have been fixed, I realized once again
how FOSS community can be reactive. And this is just amazing, impressive.
Big up to u!
So, since there are some bugs in print composer that make it hard to use
for daily and intensive compositions, can I ask for your help to fix these
ones:

- layer style in composer doesn't follow the style of the layer in canvas
when using preset (see [0] simplier expressed again here [1])
- adding a legend adds all the layers in the project and there's no quick
way to have just needed items (see [2] or [3])
- there are another bugs or ways of improvement but it would be nice if one
of the upcoming releases can fix the two listed above.

Thanks to you

[0] http://hub.qgis.org/issues/13418
[1] http://hub.qgis.org/issues/13671
[2] http://hub.qgis.org/issues/13605
[3] http://hub.qgis.org/issues/13575

[Attachment #5 (text/html)]

<div dir="ltr"><div><div><div><div><div><div>Looking at the quick way FTools bugs \
have been fixed, I realized once again how FOSS community can be reactive. And this \
is just amazing, impressive. Big up to u!<br></div>So, since there are some bugs in \
print composer that make it hard to use for daily and intensive compositions, can I \
ask for your help to fix these ones:<br><br></div>- layer style in composer \
doesn&#39;t follow the style of the layer in canvas when using preset (see [0] \
simplier expressed again here [1])<br></div>- adding a legend adds all the layers in \
the project and there&#39;s no quick way to have just needed items (see [2] or \
[3])<br></div>- there are another bugs or ways of improvement but it would be nice if \
one of the upcoming releases can fix the two listed above.<br></div><br></div>Thanks \
to you<br><div><div><div><div><div><br>[0] <a href="http://hub.qgis.org/issues/13418" \
target="_blank">http://hub.qgis.org/issues/13418</a><br>[1] <a \
href="http://hub.qgis.org/issues/13671" \
target="_blank">http://hub.qgis.org/issues/13671</a><br>[2] <a \
href="http://hub.qgis.org/issues/13605" \
target="_blank">http://hub.qgis.org/issues/13605</a><br>[3] <a \
href="http://hub.qgis.org/issues/13575" \
target="_blank">http://hub.qgis.org/issues/13575</a><br><br><br><br></div></div></div></div></div></div>



[Attachment #6 (text/plain)]

_______________________________________________
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

[prev in list] [next in list] [prev in thread] [next in thread]