[Qgis-developer] Toggle Editing Icon in Layer

[Lene Fischer]

Hi,
I´m working with 2.6,  in the Layer module. I find it difficult to see both the 
style and the editing pencil because they are on top of each other.
I realize that it save space in height, but it has become very difficult to 
read which layer are in edit mode.  Is there a special reason for this change 
of behavior from 2.4 to 2.6 ?
Regards
Lene Fischer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] processing python api change in 2.6 ?

[Vincent TINET]

I have this error message while using my scripts (no error in 2.4) on my mac

Erreur non interceptée durant l'exécution de l'algorithme
Traceback (most recent call last):
Traceback (most recent call last):
File 
"/Applications/QGIS.app/Contents/MacOS/../Resources/python/plugins/processing/core/GeoAlgorithm.py",
 line 212, in execute
self.processAlgorithm(progress)
File 
"/Applications/QGIS.app/Contents/MacOS/../Resources/python/plugins/processing/script/ScriptAlgorithm.py",
 line 264, in processAlgorithm
exec(script) in ns
File "", line 15, in 
File "/Applications/QGIS.app/Contents/MacOS/../Resources/python/qgis/utils.py", 
line 460, in _import
mod = _builtin_import(name, globals, locals, fromlist, level)
ImportError: No module named VectorWriter


I don’t understand why ?


Thanks
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] processing python api change in 2.6 ?

[Vincent TINET]

I have this error message while using my scripts (no error in 2.4) on my mac

Erreur non interceptée durant l'exécution de l'algorithme
Traceback (most recent call last):
Traceback (most recent call last):
File 
"/Applications/QGIS.app/Contents/MacOS/../Resources/python/plugins/processing/core/GeoAlgorithm.py",
 line 212, in execute
self.processAlgorithm(progress)
File 
"/Applications/QGIS.app/Contents/MacOS/../Resources/python/plugins/processing/script/ScriptAlgorithm.py",
 line 264, in processAlgorithm
exec(script) in ns
File "", line 15, in 
File "/Applications/QGIS.app/Contents/MacOS/../Resources/python/qgis/utils.py", 
line 460, in _import
mod = _builtin_import(name, globals, locals, fromlist, level)
ImportError: No module named VectorWriter


I don’t understand why ?


Thanks
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Python tests and C++ tests for the same functionality

[Nyall Dawson]

On 9 November 2014 00:30, Matthias Kuhn  wrote:
>
> (1) We could accept these deviations with anomalies or multiple
> reference images.
>
> (2) Or we could remove the C++ test in favor of the python test which
> will test the same functionality/codepath and the python binding in
> addition. That would have the advantage that maintainability will be
> easier, because not every of these tests needs to be written and
> adjusted twice. The only disatvantage I can see is that you then don't
> know if it's the python binding or the logic behind it that made a test
> fail. But that shouldn't make a big difference in the time one needs to
> debug a test.

My reservation with switching solely to the python tests is that it
makes debugging a lot more difficult. With c++ tests it's easy to run
a test from a debug session in qt creator to help track down a bug.
The workflow for python tests is a lot more difficult... (or is there
a way I'm missing of running these tests through qt creator too?).

For this reason, I'd vote for c++ tests for most methods and python
tests only when anything fancy is done is the sip bindings (transfer
of ownership, etc).

Nyall
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS 3.0?

[Roy]

**If I may** +1 for LTS or LTR

Il 08/11/2014 15.09, G. Allegri ha scritto:


+1 for LTS (2.6 or 2.8?).
A new API break risks to make users (and plugin developers) quite nervous!



IMHO as an user myself i think that a working tool is more valuable than 
a new tool,


E.G. the coming QEP from Nyall (about Composer refactoring) breaks 
Composer gui API, while it should mantain core. This could be included 
in an LTS release, while in QGIS 3.0 back compatibility can be discarded.


Just a question: typically an LTS brings backport updates during its 
lifetime. In case of QGIS how would this happen? Will we provideca new 
packaging for that release with a scheduling following the master release?




always **if i can** and**IMHO** an LTS should be a tool that you know 
you can relay on
with known and expected behavior so no new feature only bugfix or 
critical bugfix


Best regards, and thanks for your great work,

Roy.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] issues in QGIS 2.6 when saving/working with projects saved in previous QGIS releases

[Roy]

Il 08/11/2014 17.26, Giovanni Manghi ha scritto:

try (backup) and delete the .qgis2 folder, I have seen this a lot on
qgis installations where qgis was previously installed, and purging
.qgis2 usually works.


Great !!!   :) Now it works.I will test inserting plugins one by
one.

I have not investigated deeply, but in this cases it may not be a
plugin, but some (old) configuration stored inside .qgis2.


I had two crashes (with qgis project file empty) in a row applying a 
"rule-based"
style (old 2.2/2.4 QGIS style modified with QGIS 2.6) to a vector layer 
and saving

the project (brand new 2.6 project) but i can't reproduce it now;
maybe something related to styles. This **may** explain why removig 
".qgis" folder

(and related style database) seems to work...

regards,

Roy.

Roy.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Field Calculator "permanence"

[Andreas Neumann]

Hi Zoltan,

There are many other file formats besides shapes, including many 
databases. So people should stop thinking that the universe only circles 
around shapefiles.


With these other file formats it is not very common to ship other files 
along with the main file.


Why do you think that drag/drop or "add layer" is unintuitive. Those are 
the normal ways to load a layer in QGIS.


Andreas


On 07.11.2014 18:49, Zoltan Szecsei wrote:

On 2014/11/07 19:19, Zoltan Szecsei wrote:
Thanks for the pointer to 'Save Layer Definition file' - I've never 
noticed that, so I'll play with that for a bit.



On 2014/11/07 18:59, Andreas Neumann wrote:


However, if you save a layer definition file along with the 
shapefile and re-add that, they are preserved. So you can just store 
the layer definition file along with the shape and you are fine to 
share the data with your colleagues, preserving virtual fields ;-)

Hi,
OK - not very intuitive, (to have to either drag and drop the qlr file 
into the layer panel, or to "add layer from definition file")


Any reason that QGIS can't be made to look for qlr files when opening 
the SHP file "the normal way"?


Regards & thanks for the help.
Zoltan



Andreas

On 07.11.2014 17:32, Zoltan Szecsei wrote:

Hi Andreas,
I'll fiddle with the Postgis idea - thanks.
The orange part below:
I closed the shapefile, deleted from legend and re-opened it - but 
could not see my virtual field, nor the expression I used to create it.

Have I missed a trick somewhere?

Regards,
Z

On 2014/11/07 18:25, Andreas Neumann wrote:

Hi,

What you probably ask for are database triggers combined with 
storage. This is not what virtual fields are for. If they were 
stored - they wouldn't be called virtual ;-)


You can do that f.e. with Postgis. With shapefiles not. However, 
if you share the project with the other PC, the virtual fields 
work fine.


Andreas

On 07.11.2014 17:21, Zoltan Szecsei wrote:

Hi Matthias,
Thanks for the quick answer.
The virtual field acts just like I want it to, except that it 
does not permanently store the column in the attribute table.
I tried getting clever by then adding a second 'Field 
Calculation' to update the existing 'Sheet' field from the 
virtual field, but that won't do it either.


So, for me there are two shortcomings:

 1. To be able to store and recall the 'Expression' and not lose
it after closing the Field Calculator
 2. To be able to add the virtual fields that you create, into
the attribute table.
 3. (And then of course to re-open the Shape file on another PC
and have these Field Calculations still functional)

Any further possibilities I can try?

Regards & thanks again,
Zoltan


On 2014/11/07 18:01, Matthias Kuhn wrote:

Hi Zoltan,

Since QGIS 2.6 this possibility exists. It is called "Virtual Field".
You must not create the attribute when creating the shapefile. Just open
the field calculator, create a new field in there and check the "virtual
field" checkbox.

Regards,
Matthias

On 07.11.2014 16:54, Zoltan Szecsei wrote:

Hi,
I'm using QGIS 2.6.0 on Win 7 x64 - installed via OSGEO4w

Is there a way to store your field calculator expression to always
process and update that specific field, should geometry be edited or
created for that Layer?

Let's say I want to create a blank POINT shape file, with a text
attribute called "Sheet".
Whenever a POINT is created or moved, I want this field to be
dynamically updated with:

  tostring(abs(toint($y)))+tostring(abs(toint($x)))

For testing thus far have:

   * created 2 points
   * Opened the field calculator, clicked 'Update Existing Field' and
 put in the expression.
   * The two existing points now have the correct TEXT values in the
 Sheet field
   * I close the Field calculator
   * Create a new point in my layer
   * open the attribute table to find that the 'Sheet' field for this
 new point is blank
   * I open the Field Calculator and I cannot even find a way to call
 back the previous expression I used.


Am I using the correct QGIS functionality to achieve what I need to,
and if so, where am I going wrong?

Thanks & regards,
Zoltan


--

===
Zoltan Szecsei PrGISc [PGP0031]
Geograph (Pty) Ltd.
GIS and Photogrammetric Services

P.O. Box 7, Muizenberg 7950, South Africa.

Mobile: +27-83-6004028
Fax:+27-86-6115323www.geograph.co.za
===


___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer



--

===
Zoltan Szecsei PrGISc [PGP0031]
Geograph (Pty) Ltd.
GIS and Photogrammetric Services

P.O. Box 7, Muizenberg 7950, South Africa.

Mobile: +27-83-6004028
Fax:+27-86-6115323www.geograph.co.za
===


___
Qgis-developer mailing list
Qgis-developer@lists.osg

Re: [Qgis-developer] issues in QGIS 2.6 when saving/working with projects saved in previous QGIS releases

[Giovanni Manghi]

>> try (backup) and delete the .qgis2 folder, I have seen this a lot on
>> qgis installations where qgis was previously installed, and purging
>> .qgis2 usually works.
>
>
> Great !!!   :) Now it works.I will test inserting plugins one by
> one.

I have not investigated deeply, but in this cases it may not be a
plugin, but some (old) configuration stored inside .qgis2.


-- 
Giovanni Manghi
Faunalia.pt
Sistemas de Informação Geográfica Open Source
Portugal

Web: http://www.faunalia.pt
Email & Jabber: giovanni.man...@faunalia.pt
PGP Key available
Tel. + 351 96 7058216
--
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Python tests and C++ tests for the same functionality

[Sandro Santilli]

On Sat, Nov 08, 2014 at 03:00:18PM +, Nathan Woodrow wrote:
> Vote for 2. Python is a lot easier to test in, and no building step.

Can python tests effectively be used to find memory errors/leaks ?

--strk;
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Python tests and C++ tests for the same functionality

[Sandro Santilli]

On Sat, Nov 08, 2014 at 02:30:23PM +0100, Matthias Kuhn wrote:

> While working on the test suite and trying to get all tests to pass I
> realized that there are a lot of tests that exist in two versions: C++
> and python (e.g. composerhtml, atlas composition). The problem with that
> is, that they work on the same set of reference images and either one or
> the other fails because of slight inconsistencies in the result (nothing
> we should worry about, see e.g. [1]). I don't know exactly, what the
> source of these is, I assume that either there are some
> rounding/floating point differences in the python API or that meanwhile
> one or the other test was modified but not both synchroneously.
> 
> What can we do?

I think it'd be useful to figure out the source of the problem before
deciding on a solution. 

--strk;
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Python tests and C++ tests for the same functionality

[Nathan Woodrow]

Vote for 2. Python is a lot easier to test in, and no building step.

On Sat, Nov 8, 2014, 11:30 PM Matthias Kuhn  wrote:

> Hi,
>
> While working on the test suite and trying to get all tests to pass I
> realized that there are a lot of tests that exist in two versions: C++
> and python (e.g. composerhtml, atlas composition). The problem with that
> is, that they work on the same set of reference images and either one or
> the other fails because of slight inconsistencies in the result (nothing
> we should worry about, see e.g. [1]). I don't know exactly, what the
> source of these is, I assume that either there are some
> rounding/floating point differences in the python API or that meanwhile
> one or the other test was modified but not both synchroneously.
>
> What can we do?
>
> (1) We could accept these deviations with anomalies or multiple
> reference images.
>
> (2) Or we could remove the C++ test in favor of the python test which
> will test the same functionality/codepath and the python binding in
> addition. That would have the advantage that maintainability will be
> easier, because not every of these tests needs to be written and
> adjusted twice. The only disatvantage I can see is that you then don't
> know if it's the python binding or the logic behind it that made a test
> fail. But that shouldn't make a big difference in the time one needs to
> debug a test.
>
> My favorite is (2).
>
> Are there any thoughts from other devs/authors of these tests?
>
> Best
> Matthias
>
> [1] http://dash.orfeo-toolbox.org/testDetails.php?test=26809858&;
> build=162985
>
> --
> Help getting QGIS to the next level of quality before November 15!
> http://blog.vitu.ch/10102014-1046/crowdfunding-initiative-
> automated-testing
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] issues in QGIS 2.6 when saving/working with projects saved in previous QGIS releases

[Geo DrinX]

Giovanni,


try (backup) and delete the .qgis2 folder, I have seen this a lot on
> qgis installations where qgis was previously installed, and purging
> .qgis2 usually works.
>

Great !!!   :) Now it works.I will test inserting plugins one by
one.

I updated the issue list


Thank you   :)

Roberto
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS 3.0?

[G. Allegri]

+1 for LTS (2.6 or 2.8?).
A new API break risks to make users (and plugin developers) quite nervous!

E.G. the coming QEP from Nyall (about Composer refactoring) breaks Composer
gui API, while it should mantain core. This could be included in an LTS
release, while in QGIS 3.0 back compatibility can be discarded.

Just a question: typically an LTS brings backport updates during its
lifetime. In case of QGIS how would this happen? Will we provideca new
packaging for that release with a scheduling following the master release?

giovanni
Il 08/nov/2014 13:20 "Matthias Kuhn"  ha scritto:

> Yes, 2.8 LTR is the least we need to do for users that spent time to
> update to 2.0.
>
> Matthias
>
> On 08.11.2014 12:27, Anita Graser wrote:
> > On Sat, Nov 8, 2014 at 8:01 AM, Nathan Woodrow 
> wrote:
> >> Personally I think we should still do 2.8, LTR it, and then we can do
> 3.0
> >> for the next release.
> >>
> >> Breaking the API again without a LTR in place makes me nervous as the
> 2.0
> >> API really wasn't that long ago.
> >
> > +1 and even without officially breaking the API, plugin devs have been
> > quite busy with other changes which kept breaking plugins such as
> > multi-threaded rendering.
> >
> >
> > Best wishes,
> > Anita
> > ___
> > Qgis-developer mailing list
> > Qgis-developer@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
> --
> Help getting QGIS to the next level of quality before November 15!
> http://blog.vitu.ch/10102014-1046/crowdfunding-initiative-automated-testing
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Python tests and C++ tests for the same functionality

[Matthias Kuhn]

Hi,

While working on the test suite and trying to get all tests to pass I
realized that there are a lot of tests that exist in two versions: C++
and python (e.g. composerhtml, atlas composition). The problem with that
is, that they work on the same set of reference images and either one or
the other fails because of slight inconsistencies in the result (nothing
we should worry about, see e.g. [1]). I don't know exactly, what the
source of these is, I assume that either there are some
rounding/floating point differences in the python API or that meanwhile
one or the other test was modified but not both synchroneously.

What can we do?

(1) We could accept these deviations with anomalies or multiple
reference images.

(2) Or we could remove the C++ test in favor of the python test which
will test the same functionality/codepath and the python binding in
addition. That would have the advantage that maintainability will be
easier, because not every of these tests needs to be written and
adjusted twice. The only disatvantage I can see is that you then don't
know if it's the python binding or the logic behind it that made a test
fail. But that shouldn't make a big difference in the time one needs to
debug a test.

My favorite is (2).

Are there any thoughts from other devs/authors of these tests?

Best
Matthias

[1] http://dash.orfeo-toolbox.org/testDetails.php?test=26809858&build=162985

-- 
Help getting QGIS to the next level of quality before November 15!
http://blog.vitu.ch/10102014-1046/crowdfunding-initiative-automated-testing


___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] issues in QGIS 2.6 when saving/working with projects saved in previous QGIS releases

[Giovanni Manghi]

On Sat, Nov 8, 2014 at 8:16 AM, Geodrinx  wrote:
> In my case, on Win 7 64 bit,  QGIS 2.6 crashes with minidump each time I 
> quit, also doing nothing (that is, no project, no file loaded)
>
> It is normal ?
>
> LTS  please.


try (backup) and delete the .qgis2 folder, I have seen this a lot on
qgis installations where qgis was previously installed, and purging
.qgis2 usually works.



-- 
Giovanni Manghi
Faunalia.pt
Sistemas de Informação Geográfica Open Source
Portugal

Web: http://www.faunalia.pt
Email & Jabber: giovanni.man...@faunalia.pt
PGP Key available
Tel. + 351 96 7058216
--
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] issues in QGIS 2.6 when saving/working with projects saved in previous QGIS releases

[Geo DrinX]

http://hub.qgis.org/issues/11600


Roberto

2014-11-08 14:04 GMT+01:00 Geo DrinX :

> Hi Matthias,
>
>
>
> 2014-11-08 9:44 GMT+01:00 Matthias Kuhn :
>
>> Hi Roberto,
>>
>> Can you open a bug report for this.
>>
>
> I will do soon.
>
>
>> Please try to start QGIS with --noplugins and see if that makes a change
>> for you.
>>
>
> I just done your test.  At this link you find the capture screen and
> minidump file (the last one… :)
>
>
> https://drive.google.com/file/d/0Bwg_m86uaXY1UTlodVVEa0luZzg/view?usp=sharing
>
>
>
> Regards
>
> Roberto
>
>
>
>>
>> Regards
>> Matthias
>>
>>
>> On 08.11.2014 09:19, Geodrinx wrote:
>> > It is not vague:
>> > my QGIS 2.6 on Win 7  64 bit crashes ever when exit with a minidump.
>> >
>> > I have no plugin loaded, also.
>> >
>> > Regards
>> >
>> > Roberto
>> >
>> > Inviato da iPhone
>> >
>> > Il giorno 07/nov/2014, alle ore 15:16, Andreas Neumann <
>> a.neum...@carto.net> ha scritto:
>> >
>> >> Hi Giovanni,
>> >>
>> >> This is still too vague. We need to narrow down the issues.
>> >>
>> >> How about the plugins? Still crashes with no plugins?
>> >>
>> >> What data sources? Is MTR on or not?
>> >>
>> >> Please ask the reporter to provide more details and ask them to
>> disable all plugins and retry.
>> >>
>> >> Andreas
>> >>
>> >> On 07.11.2014 14:53, Giovanni Manghi wrote:
>> >>> Hi all,
>> >>>
>> >>> we are getting quite a lot of feedback (in the tracker, lists,
>> >>> directly, etc.) from users that are getting crashes in QGIS 2.6 when
>> >>> working/saving projects made with previous QGIS releases, ex:
>> >>>
>> >>> http://hub.qgis.org/issues/11593
>> >>>
>> >>> http://hub.qgis.org/issues/11592
>> >>>
>> >>> and others.
>> >>>
>> >>> Any one was able to find a pattern that would allow to track the
>> >>> source of the issue?
>> >>>
>> >>> cheers
>> >>>
>> >>> -- Giovanni --
>> >>> ___
>> >>> Qgis-developer mailing list
>> >>> Qgis-developer@lists.osgeo.org
>> >>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>> >> ___
>> >> Qgis-developer mailing list
>> >> Qgis-developer@lists.osgeo.org
>> >> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>> > ___
>> > Qgis-developer mailing list
>> > Qgis-developer@lists.osgeo.org
>> > http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>>
>> --
>> Help getting QGIS to the next level of quality before November 15!
>>
>> http://blog.vitu.ch/10102014-1046/crowdfunding-initiative-automated-testing
>>
>>
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] issues in QGIS 2.6 when saving/working with projects saved in previous QGIS releases

[Geo DrinX]

Hi Matthias,



2014-11-08 9:44 GMT+01:00 Matthias Kuhn :

> Hi Roberto,
>
> Can you open a bug report for this.
>

I will do soon.


> Please try to start QGIS with --noplugins and see if that makes a change
> for you.
>

I just done your test.  At this link you find the capture screen and
minidump file (the last one… :)

https://drive.google.com/file/d/0Bwg_m86uaXY1UTlodVVEa0luZzg/view?usp=sharing



Regards

Roberto



>
> Regards
> Matthias
>
>
> On 08.11.2014 09:19, Geodrinx wrote:
> > It is not vague:
> > my QGIS 2.6 on Win 7  64 bit crashes ever when exit with a minidump.
> >
> > I have no plugin loaded, also.
> >
> > Regards
> >
> > Roberto
> >
> > Inviato da iPhone
> >
> > Il giorno 07/nov/2014, alle ore 15:16, Andreas Neumann <
> a.neum...@carto.net> ha scritto:
> >
> >> Hi Giovanni,
> >>
> >> This is still too vague. We need to narrow down the issues.
> >>
> >> How about the plugins? Still crashes with no plugins?
> >>
> >> What data sources? Is MTR on or not?
> >>
> >> Please ask the reporter to provide more details and ask them to disable
> all plugins and retry.
> >>
> >> Andreas
> >>
> >> On 07.11.2014 14:53, Giovanni Manghi wrote:
> >>> Hi all,
> >>>
> >>> we are getting quite a lot of feedback (in the tracker, lists,
> >>> directly, etc.) from users that are getting crashes in QGIS 2.6 when
> >>> working/saving projects made with previous QGIS releases, ex:
> >>>
> >>> http://hub.qgis.org/issues/11593
> >>>
> >>> http://hub.qgis.org/issues/11592
> >>>
> >>> and others.
> >>>
> >>> Any one was able to find a pattern that would allow to track the
> >>> source of the issue?
> >>>
> >>> cheers
> >>>
> >>> -- Giovanni --
> >>> ___
> >>> Qgis-developer mailing list
> >>> Qgis-developer@lists.osgeo.org
> >>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
> >> ___
> >> Qgis-developer mailing list
> >> Qgis-developer@lists.osgeo.org
> >> http://lists.osgeo.org/mailman/listinfo/qgis-developer
> > ___
> > Qgis-developer mailing list
> > Qgis-developer@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
> --
> Help getting QGIS to the next level of quality before November 15!
> http://blog.vitu.ch/10102014-1046/crowdfunding-initiative-automated-testing
>
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS 3.0?

[Matthias Kuhn]

Yes, 2.8 LTR is the least we need to do for users that spent time to
update to 2.0.

Matthias

On 08.11.2014 12:27, Anita Graser wrote:
> On Sat, Nov 8, 2014 at 8:01 AM, Nathan Woodrow  wrote:
>> Personally I think we should still do 2.8, LTR it, and then we can do 3.0
>> for the next release.
>>
>> Breaking the API again without a LTR in place makes me nervous as the 2.0
>> API really wasn't that long ago.
>
> +1 and even without officially breaking the API, plugin devs have been
> quite busy with other changes which kept breaking plugins such as
> multi-threaded rendering.
>
>
> Best wishes,
> Anita
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer


-- 
Help getting QGIS to the next level of quality before November 15!
http://blog.vitu.ch/10102014-1046/crowdfunding-initiative-automated-testing

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Qt 5

[Matthias Kuhn]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Sorry, my message was a bit short. Please read my response to Nyall for
a more complete discussion.

I just want to make sure that there are no rumours that PR1676 [1] would
break anything.
Once that's in place, we can start to check if/where are problems and
draw a migration path.

The questions concerning the migration path are, when do packagers start
to compile (the official releases) against Qt5? All at the same
time/release? (To be kept in mind: Android is already compiled against
Qt5, some older distros that have old Qt4 versions may decide to switch
even sooner than newer distros because for them it's easier to compile
against Qt5 than to patch the source code for their old Qt4 version).
Will distros offer qgis-qt5 and qgis-qt4 in parallel? In terms of
project management a clear roadmap would be good. That however is mainly
driven by political questions and not by technical questions (most
likely QGIS 2.8 will be ready for Qt5). I would suggest to wait for
PR1676 to be merged PyQt5 support to be included. Then we can test and
decide based on more solid experiences.

All the best,
Matthias

[1] https://github.com/qgis/QGIS/pull/1676


On 08.11.2014 11:50, Paolo Cavallini wrote:
> Il 08/11/2014 10:15, Matthias Kuhn ha scritto:
>
> > Please don't list Qt5 in breakages.
>
> sorry, maybe I misunderstood, but thought the plugins have to be
> somewhat fixed.
> All the best.
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer

- -- 
Help getting QGIS to the next level of quality before November 15!
http://blog.vitu.ch/10102014-1046/crowdfunding-initiative-automated-testing
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJUXgiMAAoJEAnmVyKpy88LYnAH/2xhPvf7CKwLkSP911fowUzq
h/kcw47F1ElVFlNBksj5IrRS+Kmn9/v7zZ7VsSemFsvgQ9Yr1rrMLNhqfvkdTMhA
kEuzZUdXFLatp7q8C+A051WJAMtaVacjeMRdGoG7ns5A9ulUv86T8IsNWmYd6ms3
hSFuXIr37ULqlv3u1r+eKP1r0t22fG6IdujQlL64cmlNq7Tc01yBiHYLg31aRr5x
ca5ncUd5+RfdUEaYIdcuGB50n1O9Gb3O+BWECwQbGsjG2sTU2EMytIMPZvnnAE7j
ZTVssjGxmKRTel5ZN9oG0kiszINnC6ZLu82FLVEyPH8gr/AeBIQGL83Fn4U/fho=
=mbg2
-END PGP SIGNATURE-


___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Save selection as

[Jürgen E . Fischer]

Hi Anita,

On Sat, 08. Nov 2014 at 12:32:52 +0100, Anita Graser wrote:
> On Sat, Nov 8, 2014 at 11:53 AM, Paolo Cavallini  
> wrote:
> > Il 08/11/2014 10:18, Matthias Kuhn ha scritto:
> > I think this could result in unexpected outcome for the users.
> > All the best.
 
> Seems like a UX question ;-)
 
> I'm with Jürgen, it's very likely to confuse users because they don't
> realize that the had a selection and then they find that features are
> missing in the export.

But I don't have a opinion on it - there's probably no save default for it.  In
that way having the two menu entries might have been better.

Jürgen

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Norden http://www.norbit.de
QGIS release manager (PSC)  GermanyIRC: jef on FreeNode 



signature.asc
Description: Digital signature
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Save selection as

[Anita Graser]

On Sat, Nov 8, 2014 at 11:53 AM, Paolo Cavallini  wrote:
> Il 08/11/2014 10:18, Matthias Kuhn ha scritto:
>> Hi,
>>
>> I realized that the "save selection as" was moved to "save as". I
>> appreciate that because it reduces clutter in the layer tree
>> context menu. I wonder if this should be checked by default
>> whenever there is something selected on the layer? Just like the
>> field calculator checks "only update selected" by default whenever
>> there is a selection.
>
> I think this could result in unexpected outcome for the users.
> All the best.

Seems like a UX question ;-)

I'm with Jürgen, it's very likely to confuse users because they don't
realize that the had a selection and then they find that features are
missing in the export.
The field calculator behavior still catches me from time to time even
though I'm aware it exists.

Best wishes,
Anita
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS 3.0?

[Anita Graser]

On Sat, Nov 8, 2014 at 8:01 AM, Nathan Woodrow  wrote:
> Personally I think we should still do 2.8, LTR it, and then we can do 3.0
> for the next release.
>
> Breaking the API again without a LTR in place makes me nervous as the 2.0
> API really wasn't that long ago.


+1 and even without officially breaking the API, plugin devs have been
quite busy with other changes which kept breaking plugins such as
multi-threaded rendering.


Best wishes,
Anita
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS 3.0?

[Luca Manganelli]

On Sat, Nov 8, 2014 at 8:01 AM, Nathan Woodrow  wrote:
> Personally I think we should still do 2.8, LTR it, and then we can do 3.0
> for the next release.

I agree with a LTS version (what's LTR??? :-) ). It should be
important that the 2.X will not be "abbandoned" like as the last 1.X
series (1.8), with the Postgres primary key bug that remained UNFIXED
and that version was pretty useless...
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Save selection as

[Paolo Cavallini]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Il 08/11/2014 10:18, Matthias Kuhn ha scritto:
> Hi,
> 
> I realized that the "save selection as" was moved to "save as". I 
> appreciate that because it reduces clutter in the layer tree
> context menu. I wonder if this should be checked by default
> whenever there is something selected on the layer? Just like the
> field calculator checks "only update selected" by default whenever
> there is a selection.

I think this could result in unexpected outcome for the users.
All the best.

- -- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlRd9iAACgkQ/NedwLUzIr4C5wCeOQVwCB7hKL2RxFfLLzF4F/HQ
p90An3J/pEOe9BMp8cMftFJaKFlFW4Ey
=B8/d
-END PGP SIGNATURE-
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS 3.0?

[Paolo Cavallini]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Il 08/11/2014 10:15, Matthias Kuhn ha scritto:

> Please don't list Qt5 in breakages.

sorry, maybe I misunderstood, but thought the plugins have to be
somewhat fixed.
All the best.
- -- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlRd9XgACgkQ/NedwLUzIr5tGwCgiJDGvbGtLJSK9c1xuFcDnDtv
/VYAniLAGRAskF8y9o7YclcNJyxA82KC
=ERyg
-END PGP SIGNATURE-
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS 3.0?

[Matthias Kuhn]

On 08.11.2014 11:22, Nyall Dawson wrote:
>
>
> On 08/11/2014 9:05 pm, "Matthias Kuhn"  > wrote:
> >
> >
> >  *  Introducing Qt5 support in the QGIS source code does not break
> anything.
> >  *  Your distro actually shipping QGIS {2,3} compiled against Qt5 may
> > break stuff.
> >
>
> Makes sense now, thanks. However, by Debian removing Qt4, aren't we
> effectively in a situation where users are going to have a qt api
> break forced upon them, regardless of any decisions/actions we can make?
>
> Nyall
>
In terms of project management it would probably be good to have a
"recommended Qt version". To avoid the situation that certain users are
running the same version of QGIS with Qt4 others with Qt5 and therefore
some plugins work on one platform, some on others.

Debian seems to release at a rate of about 0.5/year, so we still have
more than 2 years to go before we are forced to release a Qt5 version
(we still may do it earlier if we like and we still could decide to have
a WITH_INTERNAL_QT4 CMake option ;) ).

Matthias

-- 
Help getting QGIS to the next level of quality before November 15!
http://blog.vitu.ch/10102014-1046/crowdfunding-initiative-automated-testing

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS 3.0?

[Nyall Dawson]

On 08/11/2014 9:05 pm, "Matthias Kuhn"  wrote:
>
>
>  *  Introducing Qt5 support in the QGIS source code does not break
anything.
>  *  Your distro actually shipping QGIS {2,3} compiled against Qt5 may
> break stuff.
>

Makes sense now, thanks. However, by Debian removing Qt4, aren't we
effectively in a situation where users are going to have a qt api break
forced upon them, regardless of any decisions/actions we can make?

Nyall
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS 3.0?

[Matthias Kuhn]

Hi,

The confusion comes from that there are two different things:

 * Qt5 compatibility
 * Qt5 binaries

The first one is a thing about the QGIS source code (qt5 branch).
The second one is about compiling/packaging.

The first step does not break anything. And allows to deprecate certain
features (e.g. qgshttptransaction) to allow for a smooth transition. It
is possible to write code that works with both versions.

The second step may actually break things. But that is not tied to a
version tag in our git repository but to a packagers decision.

*TL;DR:*

 *  Introducing Qt5 support in the QGIS source code does not break anything.
 *  Your distro actually shipping QGIS {2,3} compiled against Qt5 may
break stuff.

Matthias

On 08.11.2014 10:52, Nyall Dawson wrote:
>
>
> On 08/11/2014 8:15 pm, "Matthias Kuhn"  > wrote:
> >
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Hi Paolo,
> >
> > Please don't list Qt5 in breakages.
> >
>
> Hi Matthias,
>
> I'm a little confused - I was under the impression that some web
> related classes had been removed from qt5 (hence the mention of a
> possible breakage). Maybe I misinterpreted something.. If not,
> apologies for the noise.
>
> Nyall
>


-- 
Help getting QGIS to the next level of quality before November 15!
http://blog.vitu.ch/10102014-1046/crowdfunding-initiative-automated-testing


___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS 3.0?

[Nathan Woodrow]

Also PyQt4 imports won't work anymore so that would be a break right?

On Sat, Nov 8, 2014, 7:52 PM Nyall Dawson  wrote:

>
> On 08/11/2014 8:15 pm, "Matthias Kuhn"  wrote:
> >
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Hi Paolo,
> >
> > Please don't list Qt5 in breakages.
> >
>
> Hi Matthias,
>
> I'm a little confused - I was under the impression that some web related
> classes had been removed from qt5 (hence the mention of a possible
> breakage). Maybe I misinterpreted something.. If not, apologies for the
> noise.
>
> Nyall
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS 3.0?

[Nyall Dawson]

On 08/11/2014 8:15 pm, "Matthias Kuhn"  wrote:
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi Paolo,
>
> Please don't list Qt5 in breakages.
>

Hi Matthias,

I'm a little confused - I was under the impression that some web related
classes had been removed from qt5 (hence the mention of a possible
breakage). Maybe I misinterpreted something.. If not, apologies for the
noise.

Nyall
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Save selection as

[Matthias Kuhn]

Hi,

I realized that the "save selection as" was moved to "save as". I
appreciate that because it reduces clutter in the layer tree context menu.
I wonder if this should be checked by default whenever there is
something selected on the layer? Just like the field calculator checks
"only update selected" by default whenever there is a selection.

Matthias

-- 
Help getting QGIS to the next level of quality before November 15!
http://blog.vitu.ch/10102014-1046/crowdfunding-initiative-automated-testing

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS 3.0?

[Matthias Kuhn]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Paolo,

Please don't list Qt5 in breakages.

Thank you
Matthias

On 08.11.2014 09:46, Paolo Cavallini wrote:
> Il 08/11/2014 09:42, Matthias Kuhn ha scritto:
>
> > QGIS 3 should come with python 3. I don't think that python 3 can
> > be a smooth transition so this would require us to make QGIS 4 and
> > break plugins once again.
>
> > Qt5 support does not require QGIS 3.
>
> > Geometry and Composer(Layout) may need QGIS 3. But then we can as
> > well just introduce python 3 as well.
>
> I agree, LTS and reducing the number of breakages fit well together;
> concentrating breakages (Qt5, Py3, layout, etc.) in a single release
> seems a better option, especially for plugin developers.
> All the best.
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer

- -- 
Help getting QGIS to the next level of quality before November 15!
http://blog.vitu.ch/10102014-1046/crowdfunding-initiative-automated-testing
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJUXd8sAAoJEAnmVyKpy88LWb4IANOLwEjnpXVsJH9G5q2qo3s/
EWCQ2l5Ea3FmxADUiUoZVEU99OJqWdb/rKmKETMTyNU/6G0V8G3mSKYGTdJLzxhu
N0q5F768khcQOWjflHp1TfjE3+AIeZstiN5zLNhTjmYFLOFxPGnDZBlGCLvUyy4v
3t81y1jW0pQfuGoyLpD4jcC/Z2Mm9hty5mOGj1PmwZqLbU0dFyzTPko0K3B6MgXC
7dso4tgg68BwP8BKcsX2RUFkidj0jTPzgicTnxcUIkHzME+wq4FDbPezTZlBQyG6
CwxUuIzJ6hwgW2MLfiy+Vn25q1t8XpiFQxWgwQQfdwhUDDlxotgT0iAgWU+8oCc=
=tT7s
-END PGP SIGNATURE-

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS 3.0?

[Paolo Cavallini]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Il 08/11/2014 09:42, Matthias Kuhn ha scritto:

> QGIS 3 should come with python 3. I don't think that python 3 can
> be a smooth transition so this would require us to make QGIS 4 and
> break plugins once again.
> 
> Qt5 support does not require QGIS 3.
> 
> Geometry and Composer(Layout) may need QGIS 3. But then we can as
> well just introduce python 3 as well.

I agree, LTS and reducing the number of breakages fit well together;
concentrating breakages (Qt5, Py3, layout, etc.) in a single release
seems a better option, especially for plugin developers.
All the best.
- -- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlRd2HMACgkQ/NedwLUzIr7b8QCfflPN99RK5BxENZGzS6H7A54Y
rMwAnjC8h8Vif+IPv1p7aXtX95ZirSIB
=FvGU
-END PGP SIGNATURE-
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] issues in QGIS 2.6 when saving/working with projects saved in previous QGIS releases

[Matthias Kuhn]

Hi Roberto,

Can you open a bug report for this.
Please try to start QGIS with --noplugins and see if that makes a change
for you.

Regards
Matthias


On 08.11.2014 09:19, Geodrinx wrote:
> It is not vague:
> my QGIS 2.6 on Win 7  64 bit crashes ever when exit with a minidump. 
>
> I have no plugin loaded, also. 
>
> Regards
>
> Roberto
>
> Inviato da iPhone
>
> Il giorno 07/nov/2014, alle ore 15:16, Andreas Neumann  
> ha scritto:
>
>> Hi Giovanni,
>>
>> This is still too vague. We need to narrow down the issues.
>>
>> How about the plugins? Still crashes with no plugins?
>>
>> What data sources? Is MTR on or not?
>>
>> Please ask the reporter to provide more details and ask them to disable all 
>> plugins and retry.
>>
>> Andreas
>>
>> On 07.11.2014 14:53, Giovanni Manghi wrote:
>>> Hi all,
>>>
>>> we are getting quite a lot of feedback (in the tracker, lists,
>>> directly, etc.) from users that are getting crashes in QGIS 2.6 when
>>> working/saving projects made with previous QGIS releases, ex:
>>>
>>> http://hub.qgis.org/issues/11593
>>>
>>> http://hub.qgis.org/issues/11592
>>>
>>> and others.
>>>
>>> Any one was able to find a pattern that would allow to track the
>>> source of the issue?
>>>
>>> cheers
>>>
>>> -- Giovanni --
>>> ___
>>> Qgis-developer mailing list
>>> Qgis-developer@lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer


-- 
Help getting QGIS to the next level of quality before November 15!
http://blog.vitu.ch/10102014-1046/crowdfunding-initiative-automated-testing

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS 3.0?

[Matthias Kuhn]

Hi

QGIS 3 should come with python 3. I don't think that python 3 can be a
smooth transition so this would require us to make QGIS 4 and break
plugins once again.

Qt5 support does not require QGIS 3.

Geometry and Composer(Layout) may need QGIS 3. But then we can as well
just introduce python 3 as well.

Matthias

On 08.11.2014 09:11, Geodrinx wrote:
> Hello Nathan,
>
>> Personally I think we should still do 2.8, LTR it, and then we can do
>> 3.0 for the next release. 
>>
>> Breaking the API again without a LTR in place makes me nervous as the
>> 2.0 API really wasn't that long ago.
>
> +1000  for  LTS
>
> I am with you:  please, stop to change the api. 
> If we like new functions, please add them, without change old ones. 
>
> Thank you
>
> Roberto
>
>>
>> - Nathan
>>
>> On Sat Nov 08 2014 at 4:11:34 PM Nyall Dawson > > wrote:
>>
>> Hi all,
>>
>> I'm just wondering - given a few large changes coming up, including:
>> - qt5 support, possibly breaking plugins
>> - potential composer redesign, breaking api
>> - geometry rework, where an api break would result in a better
>> foundation moving forward
>>
>> ... is it worth exploring the idea of making the next release
>> QGIS 3.0
>> and breaking API? I know the original plan was for 3.0 to coincide
>> with python 3 support, but that doesn't appear to be anywhere on the
>> horizon yet.
>>
>> Nyall
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> 
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org 
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer


-- 
Help getting QGIS to the next level of quality before November 15!
http://blog.vitu.ch/10102014-1046/crowdfunding-initiative-automated-testing

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] issues in QGIS 2.6 when saving/working with projects saved in previous QGIS releases

[Geodrinx]

It is not vague:
my QGIS 2.6 on Win 7  64 bit crashes ever when exit with a minidump. 

I have no plugin loaded, also. 

Regards

Roberto

Inviato da iPhone

Il giorno 07/nov/2014, alle ore 15:16, Andreas Neumann  ha 
scritto:

> Hi Giovanni,
> 
> This is still too vague. We need to narrow down the issues.
> 
> How about the plugins? Still crashes with no plugins?
> 
> What data sources? Is MTR on or not?
> 
> Please ask the reporter to provide more details and ask them to disable all 
> plugins and retry.
> 
> Andreas
> 
> On 07.11.2014 14:53, Giovanni Manghi wrote:
>> Hi all,
>> 
>> we are getting quite a lot of feedback (in the tracker, lists,
>> directly, etc.) from users that are getting crashes in QGIS 2.6 when
>> working/saving projects made with previous QGIS releases, ex:
>> 
>> http://hub.qgis.org/issues/11593
>> 
>> http://hub.qgis.org/issues/11592
>> 
>> and others.
>> 
>> Any one was able to find a pattern that would allow to track the
>> source of the issue?
>> 
>> cheers
>> 
>> -- Giovanni --
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
> 
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] issues in QGIS 2.6 when saving/working with projects saved in previous QGIS releases

[Geodrinx]

In my case, on Win 7 64 bit,  QGIS 2.6 crashes with minidump each time I quit, 
also doing nothing (that is, no project, no file loaded)

It is normal ?

LTS  please. 

Regards

Roberto

Inviato da iPhone

Il giorno 07/nov/2014, alle ore 14:53, Giovanni Manghi 
 ha scritto:

> Hi all,
> 
> we are getting quite a lot of feedback (in the tracker, lists,
> directly, etc.) from users that are getting crashes in QGIS 2.6 when
> working/saving projects made with previous QGIS releases, ex:
> 
> http://hub.qgis.org/issues/11593
> 
> http://hub.qgis.org/issues/11592
> 
> and others.
> 
> Any one was able to find a pattern that would allow to track the
> source of the issue?
> 
> cheers
> 
> -- Giovanni --
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS 3.0?

[Geodrinx]

Hello Nathan,

> Personally I think we should still do 2.8, LTR it, and then we can do 3.0 for 
> the next release. 
> 
> Breaking the API again without a LTR in place makes me nervous as the 2.0 API 
> really wasn't that long ago.

+1000  for  LTS

I am with you:  please, stop to change the api. 
If we like new functions, please add them, without change old ones. 

Thank you

Roberto

> 
> - Nathan
> 
> On Sat Nov 08 2014 at 4:11:34 PM Nyall Dawson  wrote:
>> Hi all,
>> 
>> I'm just wondering - given a few large changes coming up, including:
>> - qt5 support, possibly breaking plugins
>> - potential composer redesign, breaking api
>> - geometry rework, where an api break would result in a better
>> foundation moving forward
>> 
>> ... is it worth exploring the idea of making the next release QGIS 3.0
>> and breaking API? I know the original plan was for 3.0 to coincide
>> with python 3 support, but that doesn't appear to be anywhere on the
>> horizon yet.
>> 
>> Nyall
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer