Hi,
I guess in a GIS oriented product
Is necessary to avoid to mix the interface characteristics (the group is
an interface object) and the data characteristics (the shapefile is not
an interface object).
I guess more beter if add/remove dataset is separated phisically from
add/remove a
I don't think you should comparing adding group/dataset against deleting a
group/dataset legend layer. The latter is already unified via either a
single keyboard shortcut and a single mouse right-click - remove action.
On 6 Sep 2014 13:04, aperi2007 aperi2...@gmail.com wrote:
Hi,
I guess in a
* note: there is no keyboard shortcut to delete a group, doh. :)
On Sat, Sep 6, 2014 at 1:12 PM, Mathieu Pellerin nirvn.a...@gmail.com
wrote:
I don't think you should comparing adding group/dataset against deleting a
group/dataset legend layer. The latter is already unified via either a
I know this,
but my response is enlarged to a more conceptual problem.
How avoid that an user could be confusing from when it act on a logical
level of interface,
and when it act on a physical data.
I understand that removing mean always remove and so 1 only button is
better than two.
But
Hi Marco
On Thu, Aug 28, 2014 at 2:33 PM, Marco Hugentobler
marco.hugentob...@sourcepole.ch wrote:
That leaves doxygen. Why not document API breakages where the API is
documented? Sounds like the best fit ;)
It's fine to put it into doxygen. Can it also be available as a summarized
list
Hey Mathieu,
Yeah this makes sense to me. It's only really used when you have the
legend open so it's good to have it close.
- Nathan
On Sat, Sep 6, 2014 at 3:10 PM, Mathieu Pellerin nirvn.a...@gmail.com
wrote:
Greetings,
I'd like to circulate a UX proposal and see how people react.
For
ok, thank you Alexander
processinglwgeom provider released to be used also with master
processing version
regards.
Luigi Pirelli (luigi.pire...@faunalia.it - lui...@gmail.com)
On 5 September 2014 17:41, Alexander Bruy alexander.b...@gmail.com wrote:
Hi Luigi,
AFAIK refactoring of
On Sat, Sep 6, 2014 at 7:10 AM, Mathieu Pellerin nirvn.a...@gmail.com wrote:
For a very long time, QGIS' Layers toolbar has featured a Remove layer(s)
button.
Any objection to moving the button to the new layers toolbar?
Hi Mathieu,
I like the idea of moving the button. Personally, I've never
The refactoring is done, but i think Luigi is talking about the changes to
keep backwards compatibility. I tried the import redirections that Nathan
suggested, but they do not seem to fix the issue and there is still a need
to adapt plugins to the API change.
Ideas are welcome. Otherwise, you can
Thanks Salvatore,
Zoltan
On Fri, 5 Sep 2014, Salvatore Larosa wrote:
Hi,
Il 05/Set/2014 19:48 Siki Zoltan s...@agt.bme.hu ha scritto:
Dear List,
I can't find a way to get the encoding of a vector layer from python.
Can someone give me a tipp?
from python console:
layer =
Hi Alessandro
Finally I had some time to look at your proposal (your mail and the
proposed QEP [1]). I am not that much involved in the QGIS server
development, but the Python word in the thread subject always draws my
attention :-)
On Thu, Aug 28, 2014 at 7:49 PM, Alessandro Pasotti
Hi Andreas
On Wed, Sep 3, 2014 at 9:10 PM, Andreas Neumann a.neum...@carto.net wrote:
Hi,
I noticed that SVG symbols (from point and pattern symbology) from print
composer are exported as raster when exported as part of the map and
from the legend item. However, SVG images from the
Hi Stefan
On Tue, Sep 2, 2014 at 1:13 PM, Ziegler Stefan stefan.zieg...@bd.so.ch wrote:
It seems that the dpi parameter in render.setOutputSize(img.size(), dpi) is
not respected. For any value of dpi the line width is always the same in the
output raster. It it respected when using map
Maybe also put Duplicate layer button to this new legend toolbar?
2014-09-06 12:13 GMT+03:00 Anita Graser anitagra...@gmx.at:
On Sat, Sep 6, 2014 at 7:10 AM, Mathieu Pellerin nirvn.a...@gmail.com wrote:
For a very long time, QGIS' Layers toolbar has featured a Remove layer(s)
button.
Any
hi, i've searched for info about this topic, but i didn't find anything.
so please, is there anyone who can explain how adding some existing modules
in saga 2.1.2 into processing?
infact, in this last version of saga there are some very useful modules, in
my opinion, that could be available via
You just have to add a new text file to
the processing\algs\saga\description folder
The syntax of the file is the same used for GRASS algorithms, which is
described here
https://github.com/qgis/QGIS/blob/master/python/plugins/processing/algs/grass/grass.txt
Hope this helps
2014-09-06 21:40
16 matches
Mail list logo
