Plugin qpals approval by zimbogisgeek.
The plugin version "[1287] qpals 1.5.1" is now approved
Link: http://plugins.qgis.org/plugins/qpals/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo
Is there a consensus on the pros and cons of the three different systems
mentioned so far?
On 20/11/17 20:21, Luca Manganelli wrote:
On Mon, Nov 20, 2017 at 8:19 AM, Patrick Dunford
mailto:enzedrailm...@gmail.com>> wrote:
Good day
Is there any consideration to using AppImage packagi
On 20-11-17 08:19, Patrick Dunford wrote:
> Good day
>
> Is there any consideration to using AppImage packaging for Qgis in future.
>
> Obviously we see the ability to have multiple versions installed and be
> able choose between them as a key advantage of AppImage.
Matthias did some experiments
Oh, I'm just giving you the opportunity to say "this is not a bug, it's
expected the project file format has changed" or something like that?
On 20/11/17 20:22, Andreas Neumann wrote:
Hi Patrick,
Can you please file an issue report and provide some sample data and
project to demonstrate the
Hi Patrick,
Can you please file an issue report and provide some sample data and
project to demonstrate the issue?
It would help the devs to fix this issue, if it is reproducible.
Thanks,
Andreas
On 2017-11-20 08:18, Patrick Dunford wrote:
> I have a project that (I just discovered) has
On Mon, Nov 20, 2017 at 8:19 AM, Patrick Dunford
wrote:
> Good day
>
> Is there any consideration to using AppImage packaging for Qgis in future.
>
> Obviously we see the ability to have multiple versions installed and be
> able choose between them as a key advantage of AppImage.
>
+
1. For me
Good day
Is there any consideration to using AppImage packaging for Qgis in future.
Obviously we see the ability to have multiple versions installed and be
able choose between them as a key advantage of AppImage.
Thoughts?
___
QGIS-Developer mailing
I have a project that (I just discovered) has some layers in EPSG 4326,
the project is EPSG 3857
When I changed the project from EPSG 4326 to EPSG 3857 these layers were
being reprojected on the fly, all the others were resaved into EPSG 3857
Everything has been working fine on 2.14, 2.16, 2.18
I heard these suggestions, but my project has a very short life, so I
haven't got the time to experiment really.
On 17/11/17 23:38, Even Rouault wrote:
On vendredi 17 novembre 2017 23:14:19 CET Patrick Dunford wrote:
> I understand (especially with the other comments about the functionality
Hi Anjo,
Can you look in the about menu, there is a plugin entry, see if qgis custom
widgets are listed there as broken.
If so, can you try
ldd /lib64/qt4/plugins/designerlibqgis_customwidgets.so
Cheers
Denis
Le dim. 19 nov. 2017 à 12:00, anjo.weichbrodt a
écrit :
> Hi Matthias,
>
> libqgis_c
Hi Alessandro
On Sun, Nov 19, 2017 at 10:34 AM, Alessandro Pasotti wrote:
> Hi,
>
> mi recent experiments with multi-threaded python wrappers for QGIS server
> showed a critical flaw in my original implementation of the server plugins.
>
> First, I want to stress that this is not a problem in FCG
Hi,
IMHO, The multi process approach has to be preferred over multi-threading
Some thought about it:
Forking sever instance for each request is imho a bad idea as it is not
scalable and defeat resource control.
I think that it is not a problem by itself to consider the server engine as
sin
Hi Matthias,
libqgis_customwidgets.so seems to be in the right location.
[anjo@anjo-pc ~]$ cd /lib64/qt4/plugins/designer/
[anjo@anjo-pc designer]$ ls
libpyqt4.so libqt3supportwidgets.so
libqdeclarativeview.solibqwebview.so
libqgis_customwidgets.so libq
Maybe I've found a simple and effective no-API-break solution: I'm working
on a QThreadStorage based implementation of the server iface request
handler that might be the simplest solution to this issue.
Btw this is only one of the most obvious issues in the server thread
safety, there are certainl
I didn't follow, shared cache is a solved problem for the server?
Luigi Pirelli
**
* LinkedIn: https://www.linkedin.com/in/luigipirelli
* Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pi
Hi,
mi recent experiments with multi-threaded python wrappers for QGIS server
showed a critical flaw in my original implementation of the server plugins.
First, I want to stress that this is not a problem in FCGI server
implementation but only if the server is used directly from python in a
multi
16 matches
Mail list logo
