[QGIS-Developer] Plugin [1480] arrayPlus approval notification.

[noreply]

Plugin arrayPlus approval by pcav.
The plugin version "[1480] arrayPlus 1.3" is now approved
Link: http://plugins.qgis.org/plugins/arrayplus/
___
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] Qt 6 plans

[Nyall Dawson]

Hey all,

The Qt project have recently been discussing plans for the next major
release (Qt 6). This blog post is a summary of their current plans:

https://tsdgeos.blogspot.com/2018/06/qt-contributor-summit-2018.html

It all seems quite good from a QGIS perspective, and unlikely to be as
large a porting effort as Qt 5 was.

If their time frame of November 2020 for a first release is kept (and
we wait for Qt 6 for QGIS 4.0) then we'd be probably be looking
roughly at a late 2021-mid 2022 timing for QGIS 4.0. (Put it in your
calendars now so you don't forget to install the new version.)

Nyall
___
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] Adding Map layer to current project destroy custom layer variables in Qgis3

[David Marteau]

Just found out that this is not addMapLayer that remove the variables but 
'layer.loadNamedStyle'

Print layer.customProperty('variableNames') just before calling 
'layer.loadNamedStyle' show variables
Print layer.customProperty('variableNames') just after the call :  empty list

Reproduced in the python console:

>>> QgsExpressionContextUtils.setLayerVariable(layer,'FOO','BAR')
>>> layer.customProperty('variableNames')
['FOO']
>>> layer.loadNamedStyle('mystyle.qml')
('', True)
>>> layer.customProperty('variableNames')
[]


> Le 20 juin 2018 à 18:13, David Marteau  a écrit :
> 
> Hi
> 
> I'm trying to set custom layers variables from processing using  
> QgsExpressionContextUtils.setLayerVariables to destination layers , I have 
> found that those variables does not appear in 
> Qgis. 
> 
> I have found that when the layer is inserted in the current project 
> (https://github.com/qgis/QGIS/blob/master/python/plugins/processing/gui/Postprocessing.py#L81
>  
> )
>  the layer variables are removed - Checking existence of the variable before
> and after the call of 'addMaperLayer' shows that layer variables are removed 
> from custom properties.
> 
> I cannot tell if this is a bug or not because it seems that the removal may 
> occurs in some signal handler. So if somebody has some clues to where to 
> look, I will be grateful.
> 
> 
> Qgis version: 3.0.3-Girona
> 
> David

___
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] Adding Map layer to current project destroy custom layer variables in Qgis3

[David Marteau]

Hi

I'm trying to set custom layers variables from processing using  
QgsExpressionContextUtils.setLayerVariables to destination layers , I have 
found that those variables does not appear in 
Qgis. 

I have found that when the layer is inserted in the current project 
(https://github.com/qgis/QGIS/blob/master/python/plugins/processing/gui/Postprocessing.py#L81
 
)
 the layer variables are removed - Checking existence of the variable before
and after the call of 'addMaperLayer' shows that layer variables are removed 
from custom properties.

I cannot tell if this is a bug or not because it seems that the removal may 
occurs in some signal handler. So if somebody has some clues to where to look, 
I will be grateful.


Qgis version: 3.0.3-Girona

David___
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] 2.18 and 3.x Fix regression in Legend Composer : PR 7260

[René-Luc Dhont]

Hi Dev,

I have proposed to fix a regression in Legend Composer for release-2_18 
and in release-3_x. This feature is probaby not well known by QGIS devs 
and users because it has never been documented.


In QGIS 2.0, I have introduced the capability to use the layer's title 
as the default layer legend name. This feature has been introduced to do 
not have to rename manually all the legend layers item in composer eahc 
time a legend is added in a composer or the layer is added.


As a QGIS user, when I load layers in my project, from Shapefiles, Gpkg 
or PostgreSQL, I do not rename them in the layer panel (the "legend") 
because I like to see the real source name. For example I keep 
"main_roads" instead of renaming to "Main roads". In this context, I 
like to use the metadata "title" property as a replacement. Inside the 
composer, I would like to have the titles used, because my exported PDF 
is for my colleague and not me.


So do you think, this regression has to befixed or not ?
https://github.com/qgis/QGIS/pull/7260

Regards,
René-Luc
___
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] Thoughts on using processing models for ETL tasks

[johnrobot]

Sorry for the late reply, I´ve been out of office for a while. I used the
weekly build of QGIS 3. I will  try again in 3.2.0 next week and open
tickets if I still get the Python errors.



--
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