[QGIS-Developer] QGIS3 & new PROJ.4

[Tobias Wendorff]

Hi there,

here [1], Kristian informs that the new (long awaited) new version of
PROJ.4 will be out soon.

Will its new version be supported by QGIS3 or isn't a support planned
right now?

Best regards,
Tobias

ref:
[1] https://lists.osgeo.org/pipermail/qgis-user/2018-January/041335.html



___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Last call for switching to github issue tracker

[Bernd Vogelgesang]

For me as a simple user, the main obstacle of posting issues in redmine  
is, that I fear to produce a duplicate, cause I didn't even learn over the  
years how to efficiently track an issue down if it already exists.

No idea if github or any other solution is better, but redmine just sucks.

My 2 cents,
Bernd

Am 12.01.2018, 16:30 Uhr, schrieb Régis Haubourg  
:


Hi all,+1 too.My main concern is that I now fail to search efficiently  
for redmine issues, because there are so many now. And this leads to  
>duplicates, or even worst, no declaring the issue because the process  
is too long.Github issues are very well indexed by google, which doesn't  
seem to be the case for redmine. (but this probably can be improved -  
>not sure how)


Régis

2018-01-12 16:06 GMT+01:00 Jorge Gustavo Rocha :

Hi,

Good point, Denis!

Mathias already have done a lot to support the migration.
I volunteer to help on this task.

Regards,

Jorge Gustavo

On 12-01-2018 14:49, Matthias Kuhn wrote:

On 01/12/2018 03:31 PM, Andreas Neumann wrote:


Hi,

I think the biggest question: who does all the work to migrate from
Redmine to Github while not loosing all our history?



I started working on it some time ago and thought it looked quite
promising. I stopped the work because of lack of conviction that  
there's

a perspective for this.


And I don't think that Redmine is so bad usability wise. I agree, the
UI is not as sexy as Github, but it does its job well. It is much more
powerful for finding and filtering. The issues we had with the slow
performance was fixed when moving to a new Machine at Hetzner. The
main argument for github is in my opinion not ease of use - but the
integration with the code base - that is definitely a strength of
github issue reporting.


Agreed, it's better than before.
Because no more mantra, usable performance.
On the other hand I don't prefer it's search and filtering options.


To undermine that github is not easy to use for non-dev users: last
Wednesday at the Swiss QGIS user meeting I was in the meeting for
QWC2. Users had no idea at all how Github works and could be used for
issue reporting. One had to explain it to them and teach them how to
use it. To assume that using github is self-explanatory for non-tech
users is a wrong assumption.



I wouldn't claim that for either of the two platforms. There's a
learning curve for both. Myself, I happen to meanwhile embrace markdown
but struggle with the redmine syntax. Not because it's worse, just
because I am too lazy to learn another one.

Matthias

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer



J. Gustavo
--
Jorge Gustavo Rocha
Departamento de Informática
Universidade do Minho
4710-057 Braga
Tel: +351 253604480
Fax: +351 253604471
Móvel: +351 910333888
skype: nabocudnosor
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer






--
Bernd Vogelgesang
Siedlerstraße 2
91083 Baiersdorf/Igelsdorf
Tel: 09133-825374___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Last call for switching to github issue tracker

[Régis Haubourg]

Hi Loïc,
using both gitlab and github, I'd definitly would be in favor of gitlab,
which would allow us to host our own servers. That would imply a big task
switching travis to gitlab-ci.
Cheers
Régis


2018-01-12 18:21 GMT+01:00 L.Bartoletti :

> On 12.01.2018 14:52, Denis Rouzaud wrote:
>
>> Hi all,
>>
> Hi,
>
>> I'ld like to raise a last call to switch to github issue tracker before
>> the release.
>> I'd like to summarize briefly why.
>>
>> Pros (to me):
>> - integration with code and mainly with PR
>> - avoid multiplication of platforms
>> - so much more powerful (attachment, text formatting, referecing
>> issue/PR, pinging people, fitlering/searching/tagging, possibility to
>> plugin external issue management such as zenhub or others)
>> - so much more responsive, mobile friendy and easy to use
>>
> Totally +1
> When I show in formations where you have to / can make reports, ask
> questions, etc., the users - who are not all power users, far from it... -
> prefer user-friendly interfaces and a single source easily googleable.
> Apart from the different forums or stackexchange, GitHub is the best place
> to do this.
>
> - Github has a close-source [...] I guess it leads down to pragmatic vs
>> ethical matters.
>>
> Open question: How do you feel, (Have you ever had any thoughts), about
> migrate to gitlab (and using github as a mirror)?
>
> Regards.
>
> Loïc
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Last call for switching to github issue tracker

[L.Bartoletti]

On 12.01.2018 14:52, Denis Rouzaud wrote:

Hi all,

Hi,
I'ld like to raise a last call to switch to github issue tracker 
before the release.

I'd like to summarize briefly why.

Pros (to me):
- integration with code and mainly with PR
- avoid multiplication of platforms
- so much more powerful (attachment, text formatting, referecing 
issue/PR, pinging people, fitlering/searching/tagging, possibility to 
plugin external issue management such as zenhub or others)

- so much more responsive, mobile friendy and easy to use

Totally +1
When I show in formations where you have to / can make reports, ask 
questions, etc., the users - who are not all power users, far from it... 
- prefer user-friendly interfaces and a single source easily googleable.
Apart from the different forums or stackexchange, GitHub is the best 
place to do this.


- Github has a close-source [...] I guess it leads down to pragmatic 
vs ethical matters.
Open question: How do you feel, (Have you ever had any thoughts), about 
migrate to gitlab (and using github as a mirror)?


Regards.

Loïc
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Last call for switching to github issue tracker

[Régis Haubourg]

Hi all,
+1 too.
My main concern is that I now fail to search efficiently for redmine
issues, because there are so many now. And this leads to duplicates, or
even worst, no declaring the issue because the process is too long.
Github issues are very well indexed by google, which doesn't seem to be the
case for redmine. (but this probably can be improved - not sure how)

Régis

2018-01-12 16:06 GMT+01:00 Jorge Gustavo Rocha :

> Hi,
>
> Good point, Denis!
>
> Mathias already have done a lot to support the migration.
> I volunteer to help on this task.
>
> Regards,
>
> Jorge Gustavo
>
> On 12-01-2018 14:49, Matthias Kuhn wrote:
> > On 01/12/2018 03:31 PM, Andreas Neumann wrote:
> >>
> >> Hi,
> >>
> >> I think the biggest question: who does all the work to migrate from
> >> Redmine to Github while not loosing all our history?
> >>
> >
> > I started working on it some time ago and thought it looked quite
> > promising. I stopped the work because of lack of conviction that there's
> > a perspective for this.
> >
> >> And I don't think that Redmine is so bad usability wise. I agree, the
> >> UI is not as sexy as Github, but it does its job well. It is much more
> >> powerful for finding and filtering. The issues we had with the slow
> >> performance was fixed when moving to a new Machine at Hetzner. The
> >> main argument for github is in my opinion not ease of use - but the
> >> integration with the code base - that is definitely a strength of
> >> github issue reporting.
> >
> > Agreed, it's better than before.
> > Because no more mantra, usable performance.
> > On the other hand I don't prefer it's search and filtering options.
> >
> >> To undermine that github is not easy to use for non-dev users: last
> >> Wednesday at the Swiss QGIS user meeting I was in the meeting for
> >> QWC2. Users had no idea at all how Github works and could be used for
> >> issue reporting. One had to explain it to them and teach them how to
> >> use it. To assume that using github is self-explanatory for non-tech
> >> users is a wrong assumption.
> >>
> >
> > I wouldn't claim that for either of the two platforms. There's a
> > learning curve for both. Myself, I happen to meanwhile embrace markdown
> > but struggle with the redmine syntax. Not because it's worse, just
> > because I am too lazy to learn another one.
> >
> > Matthias
> >
> > ___
> > QGIS-Developer mailing list
> > QGIS-Developer@lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> >
>
> J. Gustavo
> --
> Jorge Gustavo Rocha
> Departamento de Informática
> Universidade do Minho
> 4710-057 Braga
> Tel: +351 253604480
> Fax: +351 253604471
> Móvel: +351 910333888
> skype: nabocudnosor
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Last call for switching to github issue tracker

[Jorge Gustavo Rocha]

Hi,

Good point, Denis!

Mathias already have done a lot to support the migration.
I volunteer to help on this task.

Regards,

Jorge Gustavo

On 12-01-2018 14:49, Matthias Kuhn wrote:
> On 01/12/2018 03:31 PM, Andreas Neumann wrote:
>>
>> Hi,
>>
>> I think the biggest question: who does all the work to migrate from
>> Redmine to Github while not loosing all our history?
>>
> 
> I started working on it some time ago and thought it looked quite
> promising. I stopped the work because of lack of conviction that there's
> a perspective for this.
> 
>> And I don't think that Redmine is so bad usability wise. I agree, the
>> UI is not as sexy as Github, but it does its job well. It is much more
>> powerful for finding and filtering. The issues we had with the slow
>> performance was fixed when moving to a new Machine at Hetzner. The
>> main argument for github is in my opinion not ease of use - but the
>> integration with the code base - that is definitely a strength of
>> github issue reporting. 
> 
> Agreed, it's better than before.
> Because no more mantra, usable performance.
> On the other hand I don't prefer it's search and filtering options.
> 
>> To undermine that github is not easy to use for non-dev users: last
>> Wednesday at the Swiss QGIS user meeting I was in the meeting for
>> QWC2. Users had no idea at all how Github works and could be used for
>> issue reporting. One had to explain it to them and teach them how to
>> use it. To assume that using github is self-explanatory for non-tech
>> users is a wrong assumption.
>>
> 
> I wouldn't claim that for either of the two platforms. There's a
> learning curve for both. Myself, I happen to meanwhile embrace markdown
> but struggle with the redmine syntax. Not because it's worse, just
> because I am too lazy to learn another one.
> 
> Matthias
> 
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> 

J. Gustavo
-- 
Jorge Gustavo Rocha
Departamento de Informática
Universidade do Minho
4710-057 Braga
Tel: +351 253604480
Fax: +351 253604471
Móvel: +351 910333888
skype: nabocudnosor
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Shouldn't $area return values in the measument units of the project

[Alexandre Neto]

Hi,

I am fighting this again. Looking at the $area function description it says:

"Returns the area of the current feature. The area calculated by this
function respects both the current project's ellipsoid setting and area
unit settings. For example, if an ellipsoid has been set for the project
then the calculated area will be ellipsoidal, and if no ellipsoid is set
then the calculated area will be planimetric."

But whatever I do in the project properties, $area always returns me the
results in the same unit, the layer's units. But if I check the measurement
tools and the derived area in the feature identify results, the values are
converted to the unit I have chosen.

The project and the layer are at the same CRS which is in feet.

What is wrong?
- the $area function?
- It's description?
- Or me?

thanks!

Alexandre Neto



-- 
Alexandre Neto
-
@AlexNetoGeo
http://sigsemgrilhetas.wordpress.com
http://gisunchained.wordpress.com
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Last call for switching to github issue tracker

[Matthias Kuhn]

On 01/12/2018 03:31 PM, Andreas Neumann wrote:
>
> Hi,
>
> I think the biggest question: who does all the work to migrate from
> Redmine to Github while not loosing all our history?
>

I started working on it some time ago and thought it looked quite
promising. I stopped the work because of lack of conviction that there's
a perspective for this.

> And I don't think that Redmine is so bad usability wise. I agree, the
> UI is not as sexy as Github, but it does its job well. It is much more
> powerful for finding and filtering. The issues we had with the slow
> performance was fixed when moving to a new Machine at Hetzner. The
> main argument for github is in my opinion not ease of use - but the
> integration with the code base - that is definitely a strength of
> github issue reporting. 

Agreed, it's better than before.
Because no more mantra, usable performance.
On the other hand I don't prefer it's search and filtering options.

> To undermine that github is not easy to use for non-dev users: last
> Wednesday at the Swiss QGIS user meeting I was in the meeting for
> QWC2. Users had no idea at all how Github works and could be used for
> issue reporting. One had to explain it to them and teach them how to
> use it. To assume that using github is self-explanatory for non-tech
> users is a wrong assumption.
>

I wouldn't claim that for either of the two platforms. There's a
learning curve for both. Myself, I happen to meanwhile embrace markdown
but struggle with the redmine syntax. Not because it's worse, just
because I am too lazy to learn another one.

Matthias

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Last call for switching to github issue tracker

[Tom Chadwin]

A huge +1 from me. I was too intimidated to add issues to Redmine for some
time through not understanding what some fields meant.

Tom



-
Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon 
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Last call for switching to github issue tracker

[Andreas Neumann]

Hi, 

I think the biggest question: who does all the work to migrate from
Redmine to Github while not loosing all our history? 

The migration attempts so far haven't been very convincing. 

And I don't think that Redmine is so bad usability wise. I agree, the UI
is not as sexy as Github, but it does its job well. It is much more
powerful for finding and filtering. The issues we had with the slow
performance was fixed when moving to a new Machine at Hetzner. The main
argument for github is in my opinion not ease of use - but the
integration with the code base - that is definitely a strength of github
issue reporting. 

To undermine that github is not easy to use for non-dev users: last
Wednesday at the Swiss QGIS user meeting I was in the meeting for QWC2.
Users had no idea at all how Github works and could be used for issue
reporting. One had to explain it to them and teach them how to use it.
To assume that using github is self-explanatory for non-tech users is a
wrong assumption. 

Andreas 

On 2018-01-12 14:52, Denis Rouzaud wrote:

> Hi all, 
> 
> I'ld like to raise a last call to switch to github issue tracker before the 
> release. 
> I'd like to summarize briefly why. 
> 
> Pros (to me): 
> - integration with code and mainly with PR 
> - avoid multiplication of platforms 
> - so much more powerful (attachment, text formatting, referecing issue/PR, 
> pinging people, fitlering/searching/tagging, possibility to plugin external 
> issue management such as zenhub or others) 
> - so much more responsive, mobile friendy and easy to use 
> - lower infrstructure management on QGIS team (would be available for other 
> stuff) 
> - opportunity to clean the list 
> 
> A proof that current situation is sub-optimal: 
> - people are pointing to code issues directly in comments of commits on 
> github rather than creating an issue (high chance of getting lost) 
> - people send mail to the mailing saying they have created an issue (sic) 
> - people creates new gitub repo for creating issue lists (sic again): see 
> qgis 3 API or UX changes 
> - mantra thing is a nightmare for new comers 
> 
> Why I don't agree on the raised issues to not to move to github: 
> - migration of existing issues: we have migrated a to a new redmine which 
> should make migration easier [0]. 
> - Github has a close-source: there is an API and existing tools to migrate to 
> other issue tracker [1]. I guess it leads down to pragmatic vs ethical 
> matters. 
> 
> I would be in favor of using a semi-automatic migration: 
> - move all open tickets 
> - propose a tool to migrate others on demand: like a one-click process to 
> move the features. 
> But this can be decided afterwards. 
> 
> I know PSC is (was?) against it, but I feel the majority of devs (and new 
> issue posters) are for it. 
> Sorry to hassle on the topic. Let me know if I shall shut-up forever. Or 
> raise your hand :) 
> 
> Or can we setup a loomio vote directly??? 
> 
> Best wishes, 
> Denis 
> 
> [0] https://github.com/gmontard/issue-sync-redmine-github 
> [1] Github importer for Gitlab: 
> https://docs.gitlab.com/ee/user/project/import/github.html 
> 
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Last call for switching to github issue tracker

[Matthias Kuhn]

On 01/12/2018 03:19 PM, Borys Jurgiel wrote:
> Well, I have reconciled myself with the fact we're stuck in the darks of 
> Redmine forever, but if there is still any chance for the migration, I'd not 
> hesitate for a moment of course.

I couldn't have said it better.
+1

Matthias
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Last call for switching to github issue tracker

[Jürgen E . Fischer]

Hi Denis,

On Fri, 12. Jan 2018 at 13:52:39 +, Denis Rouzaud wrote:
> - mantra thing is a nightmare for new comers

Again: osgeo ids are not a requirement to use our redmine.


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: PGP signature
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Last call for switching to github issue tracker

[Denis Rouzaud]

Hi all,

I'ld like to raise a last call to switch to github issue tracker before the
release.
I'd like to summarize briefly why.

Pros (to me):
- integration with code and mainly with PR
- avoid multiplication of platforms
- so much more powerful (attachment, text formatting, referecing issue/PR,
pinging people, fitlering/searching/tagging, possibility to plugin external
issue management such as zenhub or others)
- so much more responsive, mobile friendy and easy to use
- lower infrstructure management on QGIS team (would be available for other
stuff)
- opportunity to clean the list

A proof that current situation is sub-optimal:
- people are pointing to code issues directly in comments of commits on
github rather than creating an issue (high chance of getting lost)
- people send mail to the mailing saying they have created an issue (sic)
- people creates new gitub repo for creating issue lists (sic again): see
qgis 3 API or UX changes
- mantra thing is a nightmare for new comers

Why I don't agree on the raised issues to not to move to github:
- migration of existing issues: we have migrated a to a new redmine which
should make migration easier [0].
- Github has a close-source: there is an API and existing tools to migrate
to other issue tracker [1]. I guess it leads down to pragmatic vs ethical
matters.

I would be in favor of using a semi-automatic migration:
- move all open tickets
- propose a tool to migrate others on demand: like a one-click process to
move the features.
But this can be decided afterwards.

I know PSC is (was?) against it, but I feel the majority of devs (and new
issue posters) are for it.
Sorry to hassle on the topic. Let me know if I shall shut-up forever. Or
raise your hand :)

Or can we setup a loomio vote directly???

Best wishes,
Denis

[0] https://github.com/gmontard/issue-sync-redmine-github
[1] Github importer for Gitlab:
https://docs.gitlab.com/ee/user/project/import/github.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Options search and QStackedWidget

[Denis Rouzaud]

Hi Richard,

Looking at it!

Denis

Le ven. 12 janv. 2018 à 06:58, Richard Duivenvoorde  a
écrit :

> Hi Devs,
>
> thought to look at
> https://issues.qgis.org/issues/17812
> which is about showing 2 tabs of a QStackedWidget when you search in the
> layer properties
>
> It is showing both widgetUnsupported and another tab:
>
>
> https://github.com/qgis/QGIS/blob/master/src/app/3d/qgsvectorlayer3drendererwidget.cpp#L49
>
> I try to understand 'searchText':
>
>
> https://github.com/qgis/QGIS/blob/master/src/gui/qgsoptionsdialogbase.cpp#L212
>
> But I do not understand if the problem is in the searching or the use of
> the QStackedWidget
>
> Anybody can give me a pointer on how this searching in all the widgets
> should work?
>
> Regards,
>
> Richard Duivenvoorde
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] QGIS Options search and QStackedWidget

[Richard Duivenvoorde]

Hi Devs,

thought to look at
https://issues.qgis.org/issues/17812
which is about showing 2 tabs of a QStackedWidget when you search in the
layer properties

It is showing both widgetUnsupported and another tab:

https://github.com/qgis/QGIS/blob/master/src/app/3d/qgsvectorlayer3drendererwidget.cpp#L49

I try to understand 'searchText':

https://github.com/qgis/QGIS/blob/master/src/gui/qgsoptionsdialogbase.cpp#L212

But I do not understand if the problem is in the searching or the use of
the QStackedWidget

Anybody can give me a pointer on how this searching in all the widgets
should work?

Regards,

Richard Duivenvoorde
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] set unspecified precision -1 on double in spatiaLite and org providers

[Matthias Kuhn]

Hi Dave,

the proposal is that

QgsFields::precision() always returns -1 for doubles, correct?

Sounds fine to me, 0 might be a real value (0 digits after the decimal
point) while -1 clearly indicates an arbitrary precision (as in double).

Matthias


On 01/09/2018 03:34 PM, David Signer wrote:
> Hi all
>
> We found different behaviors in qgsorgprovider and
> qgsspatialiteprovider regarding the field with the type double.
> In `QgsSpatiaLiteProvider::convertField` it's set to -1 when it's 0 :
> https://github.com/qgis/QGIS/blob/master/src/providers/spatialite/qgsspatialiteprovider.cpp#L82-L88
> That's why I decided to change it in
> `QgsSpatiaLiteProvider::loadFieldsAbstractInterface` as well. The
> advantage would be, that we could recognize a field with type double
> when the precision is not zero.
> But when I checked qgsorgprovider, in `QgsOgrProvider::convertField`
> the precision is not set (stays what it is) in case of double:
> https://github.com/qgis/QGIS/blob/master/src/providers/ogr/qgsogrprovider.cpp#L143-L145
> I wonder why it's different and I ask you, if you mind, when we just
> set the precision in any case to -1 when it's a double value and it's
> not specified (means 0)?
>
> Thanks 
> Dave
>
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer