On Tue, Feb 19, 2013 at 4:48 AM, Mathieu Pellerin nirvn.a...@gmail.com wrote:
Radim,
Following up on your implementation of the nice legend's multicolumn
feature. I've noticed two regression (one of which I've filed a bug
already).
1) The right-side box spacing is now miscalculated as it
Radim,
Thanks for fixing the width issue.
Regarding layers with no titles and the need for treating the space like a
layer item, see http://hub.qgis.org/issues/3605. We've discussed this with
Marco Hugentobler back then and came up with a nice compromise.
Beyond being a regression as it stands
Hello dear QGIS dev community,
my first try to use/ write into a mailing list..
Only one short question I would like to ask:
When should one expect to be able to build QGIS by using Qt5?
Any plannings ideas?
Thanks in advance
joomie (from Germany)
Hi devs
The first part of the symbology improvements is available in my github fork:
https://github.com/mhugent/Quantum-GIS/tree/data_defined_symbology
Currently, one symbol is either in mm or in map units. The changeset in
the branch adds the possibility to mix different output units ( mm /
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 11/03/2013 14:58, Matthias Kuhn ha scritto:
I'm not sure what the best way is to keep new features coming but
at the same time guarantee for stability.
I think the suggestion by Paolo Corti, to use the GeoNode way of using
git branches, is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 11/03/2013 14:14, Giovanni Manghi ha scritto:
Hi all, as discussion about the next release has already started,
so here is the periodic issue report.
Hi all.
Not a very encouraging situation: anyone is planning to act on the
specifica issues,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 13/03/2013 03:41, maning sambale ha scritto:
Dear Maris,
We don't really want to disturb existing plans nor the dev's focus
on coding. But if there is way for us to help remotely, please let
us know.
IMHO we should make it as easy as
One thing, while not directly connected to release schedules, is
the way, issue reports work. We've got now close to 2000 open
issues. More than anyone could handle. I think we need to shoot
down some of the non-issues to allow the real bugs to gain some
attention. And then keep the issue
Hi Alexandre
On Tue, Mar 12, 2013 at 1:22 AM, Alexandre Neto senhor.n...@gmail.com wrote:
...
new_attributes = layer.pendingFields()
[...]
But when using it in 1.9 I got the following error in the line:
new_attributes[j] = feature.attributes()[j]
Traceback (most recent call last):
Hi,
The WPS plugin with Sextante integration in https://www.kappasys.ch/svn/wps is
now ready for others to look into. The major work was an extraction of shared
WPS client code into a wpslib package. Testing of the native GUI is very
welcome, since a big amount of code had to be touched. The
I'd love to hear if anyone tests this against a standard geoserver wps
instance.
On Wed, Mar 13, 2013 at 2:27 PM, Pirmin Kalberer pi...@sourcepole.comwrote:
Hi,
The WPS plugin with Sextante integration in
https://www.kappasys.ch/svn/wps is
now ready for others to look into. The major work
11 matches
Mail list logo
