[Qgis-developer] Rendering bugs: QGIS or Qt?

[Denis Rouzaud]

I would say yes for #8980, but no idea for #8974.

I would let more aware people answer about Qt5.
But if we have to change to Python 3, I think it would be considered as 
an API break as older plugins might not work anymore....
So, sadly, I suspect we won't see this happening very soon, willwe?
Or maybe, if this time we take care of porting every plugins with 2to3?

I'd like to hear (read) these aware people ;)

Cheers,

Denis



On 11/06/2013 07:49 AM, Paolo Cavallini wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Il 06/11/2013 07:45, Denis Rouzaud ha scritto:
>
>> No, it also occurs in 4.8 and it's why we had troubles to have a dashed line for the
>> last segment in digitization.
>> It was solved in Qt 5.0.2 but not for Qt 4.8.
> ok, thanks. do you believe this has also fixed the other two bugs?
> in case, I suppose moving qgis to qt5 would be a major task, right?
> qt5 at least on Debian comes only with Python3, so it seems quite bloody.
> all the best.
> - -- 
> Paolo Cavallini - Faunalia
> www.faunalia.eu
> Full contact details at www.faunalia.eu/pc
> Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.15 (GNU/Linux)
> Comment: Using GnuPG with Icedove - http://www.enigmail.net/
>
> iEYEARECAAYFAlJ55o4ACgkQ/NedwLUzIr79QACdF09FDO+rLkoshedSbDledcar
> BQMAoKwJ40R7q5vM1ucDkXCkJR/JvnpT
> =iv/S
> -----END PGP SIGNATURE-----