-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
anybody willing / able to help fix this bug?
http://hub.qgis.org/issues/13374
If helpful, may be (depending on how much is needed) we could provide
some fundig / donation / sponsoring for this.
Marco
- --
Dr. Marco Lechner
Bundesamt fuer
On Sun, Oct 11, 2015 at 8:02 PM, Pedro Venâncio
wrote:
>> > I also found that saving edits with "Save edits" button in the attribute
>> > tabel takes no effect. With other layers (not GRASS layers), it works
>> > well.
>>
>> It should not take any effect, because with
On Fri, Oct 9, 2015 at 12:05 PM, matteo wrote:
> Linking CXX shared module
> ../../../../output/lib/qgis/plugins/libgrassplugin7.so
> /usr/bin/ld: cannot find -lqgisgrass7
The lib qgisgrass7 is part of src/providers/grass, so please go to
that dir and try to rebuild
Il 12/10/2015 10.06, Radim Blazek ha scritto:
> The user must have some minimum knowledge about GRASS topological
> model. Note that 'Add Area' makes only sense for isolated areas,
> common boundaries of adjacent areas must be digitized by 'Add
> Boundary' because the boundary is shared by areas
On Mon, Oct 12, 2015 at 12:02 PM, matteo wrote:
> Hi Radim,
> well in the src/providers/grass folder I have the following directories:
>
> 7 CMakeFiles
If you run 'make' in src/providers/grass/7 it compiles without error?
It should either build target qgisgrass7
> If you run 'make' in src/providers/grass/7 it compiles without error?
> It should either build target qgisgrass7 (libqgisgrass7.so) or give an
> error.
actually I get an error following your instructions:
ma7730@debian:~/lavori/QGIS/QGIS-Master/buildMaster/src/providers/grass/7$
make
make: ***
Hi Radim,
well in the src/providers/grass folder I have the following directories:
7 CMakeFiles
and actually in output/lib/qgis/plugins/ there is not any
libqgisgrass7.so file
I try to create another build directory in the repo and compile again
from scratch but I receive the same error..
Il 12/10/2015 10.06, Radim Blazek ha scritto:
> The user must have some minimum knowledge about GRASS topological
> model. Note that 'Add Area' makes only sense for isolated areas,
> common boundaries of adjacent areas must be digitized by 'Add
> Boundary' because the boundary is shared by areas
Confirmed.. after pulling the repository I'm able to work with the
field calculator.
thanks!
Matteo
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
Hi all,
I'm doing some test with Processing and I'm facing some problem with
some algorithm:
* Create grid (QGIS).. each time I try to create a grid I receive this
error:
Grid instance has no attribute 'TYPES' See log for more details
while using the same algorithm from the Vector menu of QGIS
Il 12/10/2015 17.12, Radim Blazek ha scritto:
> I think that the QGIS "Add Area" should be renamed to "Add closed boundary"
> (or something like that) because GRASS has the "Add Area" tool that in fact
> allow you to add boundary and centroid in one go;
> OK, if I don't manage to add centroid
Hi Matteo,
that was a small lack due to some changes in the translation strings.
Just fixed in master.
-SL
On Sun, Oct 11, 2015 at 4:29 PM, matteo wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi all,
> I'm trying to open and use the Field Calculator
I have opened a new ticket:
https://hub.qgis.org/issues/13579
Em seg, 12 de out de 2015 às 16:29, Saber Razmjooei <
saber.razmjo...@lutraconsulting.co.uk> escreveu:
> Might be a regression:
>
> https://hub.qgis.org/issues/13059
>
>
>
> Cheers,
>
> Saber
>
>
>
> *From:* Qgis-developer
Hi Andreas,
On Mon, 12. Oct 2015 at 13:47:03 +0200, Andreas Neumann wrote:
> I know - this discussion came up repeatedly in the past - but here I
> am, bringing it up again. Jürgen - please don't shoot me ;-)
As if that would help - there are far too many people out there ;) I just
wonder why
For the recall :
http://docs.qgis.org/2.0/en/docs/user_manual/print_composer/print_composer.html#legend-items
2015-10-12 17:51 GMT+02:00 m roy :
>
> > In previous releases (till 2.4 I think), there was another option
> > "Update item" that keeps user customization and can
Might be a regression:
https://hub.qgis.org/issues/13059
Cheers,
Saber
From: Qgis-developer [mailto:qgis-developer-boun...@lists.osgeo.org] On Behalf
Of João Gaspar
Sent: 12 October 2015 16:11
To: Alexandre Neto
Cc: qgis-dev
Subject: Re: [Qgis-developer] Crash Dump 2.11 with user
Hi Jürgen,
I don't claim that a six months release schedule solves all our issues.
I know it is not too different.
But every release is a lot of work - for packagers, translators,
testers, documenters - also for people like Anita and me who help
evangelizing/promoting QGIS. In the past I
"After changing the symbology in the QGIS main window you can click on [Update]
to adapt the changes in the legend element of the print composer"
I think that now changes in the legend element of print composer is automatic
when you change, say, layer name color,
and that was the purpose of
Il 12/10/2015 14:48, Andreas Neumann ha scritto:
> So it is a matter of time and funding. We can provide basic funding from
> QGIS.ORG - but more additional funding from third parties will mean more
> tests ;-)
Yes, that's the reason I'm spreading this out to the MLs - possibly a
clever power
Le 12/10/2015 12:15, matteo a écrit :
Hi all,
I'm doing some test with Processing and I'm facing some problem with
some algorithm:
* Create grid (QGIS).. each time I try to create a grid I receive this
error:
Grid instance has no attribute 'TYPES' See log for more details
while using the same
Hi Anita,
I know that I don't need to update every release.
By stressful - I don't only mean myself as a governmental user - but us
all (the people involved with the QGIS project). For you as well. Why do
we have to release so often? Aside from web browsers - I don't know a
single open
Hi all,
Il 12/10/2015 12:15, matteo ha scritto:
> * Create grid (QGIS).. each time I try to create a grid I receive this
> error:
> Grid instance has no attribute 'TYPES' See log for more details
>
> while using the same algorithm from the Vector menu of QGIS no problem
>
>
> * Zonal
Hi Paolo,
I thought that Matthias and Victor are already looking into the
Processing test suite and will submit a proposal to the QGIS.ORG board -
right?
So it is a matter of time and funding. We can provide basic funding from
QGIS.ORG - but more additional funding from third parties will
Hi all,
I know - this discussion came up repeatedly in the past - but here I am,
bringing it up again. Jürgen - please don't shoot me ;-)
As a QGIS user in government (you could also replace this by a company
or other professional users) I find the 4 month release schedule not
ideal - and
Hi Andreas,
On Mon, Oct 12, 2015 at 1:47 PM, Andreas Neumann
wrote:
> As a QGIS user in government (you could also replace this by a company or
> other professional users) I find the 4 month release schedule not ideal -
> and quite stressful. I would rather prefer a
Hello all,
I'm having Crash Dumps in current master, on windows 7 64 bits. After a few
tests and some .qgis2 cleaning I realized it has something to do with
expression functions created by user.
The attached file makes qgis crash dump, if you try to open the expressions
dialog.
It works in QGIS
Alexandre,
i confirm this behavior.
In Windows 7 64-bits:
OSGeo4W Installer (64-bits) QGIS Master version ac3f390
After i put your functions in the folder of expressions
.qgis2\python\expressions when i start the QGIS he starts with minidump
crash and don't open.
Regards
João
2015-10-12 15:58
This is what I'm saying.
Then, what are the benefits of having "update all" button since it does
same thing than the automatic? Why just not keep the "auto-update" option?
User checks and unchecks "auto-update" and it's okay, his items are up to
date/reset actually (though I agree checkbox is not
Thanks Andreas to raise the issue again.
I feel stressed too with that release cycle as a public enterprise manager.
Why ?
- We try to push new features and fund them. It requires to test them when
they land in master and restest them in all versions for regressions in
LTR.
- We have a
Il 12/10/2015 16.14, DelazJ ha scritto:
Hitting "update all" behaves like checking "auto-update". Have I missed
something ? Is it worth keeping both ?
Yes, one is automatic (e.g. for servers), the other update is triggered (or
not) by user choice.
Hi,
I'd like to know what are the differences between those two options
available while customizing a legend in a print composer. Except that
"auto-update" does work silently, they both do AFAICS same things :
- update list of layers according to what exists in the map canvas or map
item content
-
On Mon, Oct 12, 2015 at 1:07 PM, matteo wrote:
>> If you run 'make' in src/providers/grass/7 it compiles without error?
>> It should either build target qgisgrass7 (libqgisgrass7.so) or give an
>> error.
>
> actually I get an error following your instructions:
>
>
On Mon, Oct 12, 2015 at 6:33 PM, m roy wrote:
>>> another issue I discovered while testing QGIS digitizer with GRASS vectors
>>> is that there is no difference between node and vertex, in GRASS they have
>>> two different "topological meaning"; as it is now you can't tell
>>>
Il 12/10/2015 19.32, Radim Blazek ha scritto:
> On Mon, Oct 12, 2015 at 6:33 PM, m roy wrote:
another issue I discovered while testing QGIS digitizer with GRASS vectors
is that there is no difference between node and vertex, in GRASS they have
two different
Il 12/10/2015 20.51, Pedro Venâncio ha scritto:
2015-10-12 19:15 GMT+01:00 Pedro Venâncio
>:
Maybe this was already fixed:
https://github.com/qgis/QGIS/commit/de8b045b2647b6ceb9ca2f34e729c549419d101a
I will compile again and check.
Hi
> On 12 Oct 2015, at 18:37, Andreas Neumann wrote:
>
> Hi Jürgen,
>
> I don't claim that a six months release schedule solves all our issues. I
> know it is not too different.
>
> But every release is a lot of work - for packagers, translators, testers,
>
On Mon, Oct 12, 2015 at 10:33:15PM +0200, Tim Sutton wrote:
> Andreas how would you see the LTR releases working in relation to a slower
> release cycle? I have thought at times that we should make the LTR’s longer
> lived e.g. 2 years (1 year is not really that ‘long term’).
FWIW, I also find
2015-10-12 19:15 GMT+01:00 Pedro Venâncio :
> Maybe this was already fixed:
>
>
> https://github.com/qgis/QGIS/commit/de8b045b2647b6ceb9ca2f34e729c549419d101a
>
> I will compile again and check.
>
>
>
I confirm, this is already fixed.
Hi,
Andreas how would you see the LTR releases working in relation to a
slower release cycle? I have thought at times that we should make the
LTR’s longer lived e.g. 2 years (1 year is not really that ‘long term’).
I agree, 2 years support for the LTR releases seems more useful. But
this
Hi Jürgen and all,
On Mon, Oct 12, 2015 at 9:49 AM, Jürgen E. wrote:
> Hi Andreas,
>
> On Mon, 12. Oct 2015 at 13:47:03 +0200, Andreas Neumann wrote:
> > I know - this discussion came up repeatedly in the past - but here I
> > am, bringing it up again. Jürgen - please don't
On 12 October 2015 at 22:47, Andreas Neumann wrote:
> Hi all,
>
> So should we really keep this fast release cycle with releases every 4
> months with the risk that these in between releases are barely usable for
> professional users or should we rather have one release
41 matches
Mail list logo