Great -- seems like there's a consensus that 4.8 is the way to go.
I've made a pull request which bumps the minimum qt version to 4.8
here:
https://github.com/qgis/QGIS/pull/1006
I'll leave it to someone more senior to make the final call and merge this in.
Nyall
Hi Nyall,
On Tue, 12. Nov 2013 at 14:39:41 +1100, Nyall Dawson wrote:
What's the chance we can get the minimum qt version bumped up to 4.6?
Lucid which still isn't out of LTS has is - although that's probably not that
important.
But OSGeo4W 32bit has 4.7.1. So that would be the maximum
Dear SEXTANTE Developer,
I am a GIS enthusiast and Computer Science student and I am writing you as
I need your help within my GIS-related MSc final project (thesis).
I prepared a short questionnaire for assessing some feature of SEXTANTE as
a geo-processing framework.
It won't take you more
On 24 November 2013 21:50, Jürgen E. j...@norbit.de wrote:
But OSGeo4W 32bit has 4.7.1. So that would be the maximum version for me and
there's not much requiring 4.8 in current QGIS.
Ok - https://github.com/qgis/QGIS/pull/1007 sets the minimum version
to 4.7. Can we merge that and get the
I find the DB Manager SQL window to be unusable, and have confirmed that
it is because of syntax highlighting by disabling this feature in my
installation. There is an issue already in the tracker
https://hub.qgis.org/issues/6995 entitled db manager's SQL window
freezes with long query (due to
I can't confirm...
Try, for example, typing `SELECT 1;` into the window, and see how long it
takes you
I can't repeat the problems doing this... can you post a better test case?
Luigi Pirelli (luigi.pire...@faunalia.it)
On 24 November 2013 22:24, Lee Hachadoorian
Hi,
I can now say that the slowness problem does not only affects PostGIS layers.
It also happens to me with any kind of shapefiles (points, polylines and
polygons).
It's an erratic behavior, does not have a regular pattern, and does not always
happen. What seems to me is that only happens
Hi Lee,
On Sun, Nov 24, 2013 at 10:24 PM, Lee Hachadoorian
lee.hachadooria...@gmail.com wrote:
I find the DB Manager SQL window to be unusable, and have confirmed that
it is because of syntax highlighting [...].
[...]
This is correct in that QGIS does not completely stop responding, but
The syntax highlighting is already usable as it is, nobody else is
experiencing any issue with it... Surely it can be improved, but definitely
it's not just eye candy, as it helps in writing queries.
I don't think it's the syntax highlighting that's the issue - I think
it's related to the
On 11/24/2013 08:10 PM, Nyall Dawson wrote:
The syntax highlighting is already usable as it is, nobody else is
experiencing any issue with it... Surely it can be improved, but definitely
it's not just eye candy, as it helps in writing queries.
I don't think it's the syntax highlighting that's
On 11/24/2013 09:07 PM, Lee Hachadoorian wrote:
On 11/24/2013 08:10 PM, Nyall Dawson wrote:
The syntax highlighting is already usable as it is, nobody else is
experiencing any issue with it... Surely it can be improved, but
definitely
it's not just eye candy, as it helps in writing queries.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 25/11/2013 04:13, Lee Hachadoorian ha scritto:
It seems one person has observed what I'm talking about, and two
say they don't see the latency. If I may ask those who say they
aren't
IMHO syntax highlighting and auto completion are two
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 24/11/2013 11:50, Jürgen E. Fischer ha scritto:
But OSGeo4W 32bit has 4.7.1. So that would be the maximum version
for me and there's not much requiring 4.8 in current QGIS.
Hi Juergen,
wouldn't having two different versions, with possibly
13 matches
Mail list logo
