Bernd,
see http://hub.qgis.org/issues/13575
Envoyé depuis mon HTC
- Reply message -
De : "Bernd Vogelgesang"
Pour :
Objet : [Qgis-developer] [QGIS-UX] Composer Legend items: what are the
differences between "auto-update" and "update all" options?
Date : mer., oct. 14, 2015 23:23
Hi,
I
Bernd,
see http://hub.qgis.org/issues/13575
Envoyé depuis mon HTC
- Reply message -
De : "Bernd Vogelgesang"
Pour :
Objet : [Qgis-developer] [QGIS-UX] Composer Legend items: what are the
differences between "auto-update" and "update all" options?
Date : mer., oct. 14, 2015 23:23
Hi,
I
Hi Nyall,
On Wed, Oct 14, 2015 at 1:59 PM, Nyall Dawson
wrote:
> On 14 October 2015 at 22:31, Larry Shaffer wrote:
> > Hi,
> >
> > Seems like all protections (against force push, deleting and failing
> tests)
> > are a good fit.
> >
> > There may be instances where some tests are failing on Mac
Bernd,
see http://hub.qgis.org/issues/13575
Envoyé depuis mon HTC
- Reply message -
De : "Bernd Vogelgesang"
Pour :
Objet : [Qgis-developer] [QGIS-UX] Composer Legend items: what are the
differences between "auto-update" and "update all" options?
Date : mer., oct. 14, 2015 23:23
Hi,
I
Hi,
I'm more missing a discussion about why in fact all loaded layers are
displayed in the legend, and not only those activated in the canvas.
There is a reason why a deactivate layers: I want to produce a map only
with those active ones = shown in the map.
So why do I have to manually remove
Hi all, (Radim)
I am getting the following error on building: http://codepad.org/ZZiB2R63
Is this related to a local problem?
Anyone confirms?
Thanks,
-SL
--
Salvatore Larosa
linkedIn: http://linkedin.com/in/larosasalvatore
twitter: @lrssvt
skype: s.larosa
IRC: lrssvt on freenode
___
On 14 October 2015 at 22:31, Larry Shaffer wrote:
> Hi,
>
> Seems like all protections (against force push, deleting and failing tests)
> are a good fit.
>
> There may be instances where some tests are failing on Mac, due to an oddity
> with that platform and not with the actual code per se, i.e.
Hi Victor,
just to let you know that both r.report and v.report are working now
Thanks!
Matteo
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
On Wed, Oct 14, 2015 at 2:20 PM, Andreas Neumann
wrote:
> Hi,
>
> I am adding the UX (user interface) list about this legend discussion.
>
> The whole situation about legend updates and the current legend GUI in
> composer is indeed a bit confusing and changed quite a bit in the last one
> (or tw
Il 14/10/2015 19.01, Radim Blazek ha scritto:
> On Thu, Oct 8, 2015 at 1:07 PM, m roy wrote:
>> Vector digitizing: QGIS crash when deleting a line and the layer
>> is not longer loadable in QGIS because of broken topology,
> Fixed, it was the different off_t size in GRASS and QGIS on Windows.
>
Hi Sandro,
On Wed, 14. Oct 2015 at 18:02:50 +0200, Sandro Santilli wrote:
> Isn't the plan for 2.14 to be the Febrary 2016 LTR ?
Oops, of course - darn numbers.
What we release in February (ie. 2.14) will the be the next LTR. And it will
enter the LTR repositories when the following release is
On Thu, Oct 8, 2015 at 1:07 PM, m roy wrote:
> Vector digitizing: QGIS crash when deleting a line and the layer
> is not longer loadable in QGIS because of broken topology,
Fixed, it was the different off_t size in GRASS and QGIS on Windows.
It should work in the next nightly build 2.11.0-90.
Ra
On Wed, Oct 14, 2015 at 05:54:47PM +0200, Jürgen E. Fischer wrote:
> On Wed, 14. Oct 2015 at 14:59:11 +0300, Lauri Kajan wrote:
> > What I ment was that basically now freezed 2.12 will become the LTR in next
> > February after all its features have been tested the next four months in
> > 2.12. And
Hi Lauri,
On Wed, 14. Oct 2015 at 14:59:11 +0300, Lauri Kajan wrote:
> If I haven't understood completely wrong the initial LTR releases have new
> features just like regular releases, but no new features are added to bug
> fix release of course.
Correct.
> What I ment was that basically now fre
On Thu, Oct 8, 2015 at 4:52 PM, m roy wrote:
>> Rasters are corrupted on Windows?
> yes on windows, sorry, i forgot to state that clearly;
> I mean the raster is *not really corrupted*, it just looks weird.
Fixed. It was really the text mode output once more, introduced by
bulk WIN32 to Q_OS_WIN
Il 14/10/2015 14:52, Paolo Cavallini ha scritto:
> Hi all,
> I'm getting crashes with the module:
>
> r.contour input=dtm_loc@PERMANENT step=100 minlevel=0 maxlevel=500
> output=cont2
> Lettura dei dati in corso ...
> Modulo crashato o interrotto
More info from the log:
QFileSystemWatcher::r
Arg I meant to say feature parity between QGIS with qt4 and QGIS with qt5.
Darn smartphones.
On 14 Oct 2015 20:20, "Mathieu Pellerin" wrote:
> I really like the idea of making one of the focus of the next dev cycle to
> be qt5. Even if 2.14 is still compiled against 2.14 by default, it'd be
> gre
I really like the idea of making one of the focus of the next dev cycle to
be qt5. Even if 2.14 is still compiled against 2.14 by default, it'd be
great to attempt to reach user experience parity between 2.14 & 2.15 on the
major platforms QGIS is shipped on.
Having faced the need to compiled and u
Hey Tom,
I suspect it won't be that bad overall but we do need to just see what is
needed first. The Python 2 -> 3 change isn't so bad, there is a few things
but they are workable.
The change to PyQt5 is also workable. You could do this kind of thing for
the imports:
if version >= 3.0:
from
Hi,
On Wed, Oct 14, 2015 at 6:59 AM, Nathan Woodrow wrote:
> I don't think having Qt5 on OSX is so much the issue but the change the
> PyQt5/Python3 as that has the larger impact because it changes all the
> plugins.
>
Makes sense, especially since PyQt4 can be built against Qt4 or Qt5. Then
ma
As the developer of a single plugin, and a very inexperienced one, can I ask
how Py3/Qt5 will work? Will we require separate branches for QGIS2 and QGIS3
versions of our plugins? In other words, it is plausibly feasible to have a
single plugin codebase which will try Py3/Qt5 and fail back gracefull
I don't think having Qt5 on OSX is so much the issue but the change the
PyQt5/Python3 as that has the larger impact because it changes all the
plugins.
- Nathan
On Wed, Oct 14, 2015 at 10:57 PM, Larry Shaffer
wrote:
> Hi,
>
> On Wed, Oct 14, 2015 at 6:06 AM, Paolo Cavallini
> wrote:
>
>> Il 14
Hi,
On Wed, Oct 14, 2015 at 6:06 AM, Paolo Cavallini
wrote:
> Il 14/10/2015 13:58, Larry Shaffer ha scritto:
>
> > With regards to Mac and Qt4 support, it may be that even an LTR 2.14
> > release will have a very short lifespan, given that the next Mac OS
> > upgrade will probably significantly
Hi all,
I'm getting crashes with the module:
r.contour input=dtm_loc@PERMANENT step=100 minlevel=0 maxlevel=500
output=cont2
Lettura dei dati in corso ...
Modulo crashato o interrotto
Anyone can confirm?
All on latest master, grass7, Debian sid.
All the best.
--
Paolo Cavallini - www.faunali
Hi all,
when importing a shapefile, the resulting layer name is taken by default
== to the name of the shp, but is not dsplayed in the interface. When
clicking on Show result, nothing happens. If I give a name by hand, then
all works fine.
Should I open a ticket?
Thanks.
--
Paolo Cavallini - www.f
Hi,
I am adding the UX (user interface) list about this legend discussion.
The whole situation about legend updates and the current legend GUI in
composer is indeed a bit confusing and changed quite a bit in the last
one (or two? releases). I also think that the "Auto update" checkbox and
the
Hi all,
2015-10-14 13:16 GMT+02:00 Alexandre Neto :
> Like you said the "update all" button behaviour can be done by selecting
> and unselecting the Update checkbox. But I find it not very elegant
> solution.
>
It's indeed not very elegant nor intuitive. I've thought about a pushbutton
that woul
Il 14/10/2015 13:58, Larry Shaffer ha scritto:
> With regards to Mac and Qt4 support, it may be that even an LTR 2.14
> release will have a very short lifespan, given that the next Mac OS
> upgrade will probably significantly break Qt4; and, I seriously doubt
> there will be people wanting to resu
Hi Jürgen,
If I haven't understood completely wrong the initial LTR releases have new
features just like regular releases, but no new features are added to bug
fix release of course.
What I ment was that basically now freezed 2.12 will become the LTR in next
February after all its features have be
Hi,
On Wed, Oct 14, 2015 at 3:19 AM, Richard Duivenvoorde
wrote:
> Work hard on 2.14 AND docs for it, to be the last but most stable 2.x
> version ever by being very carefull about what put in 2.13 (maybe a
> (big)feature freeze)
> Then after 2.14 concentrate on moving to Python3/Qt5, so general
Hi,
Seems like all protections (against force push, deleting and failing tests)
are a good fit.
There may be instances where some tests are failing on Mac, due to an
oddity with that platform and not with the actual code per se, i.e. the
test needs updated for Mac or some Mac-specific bit needs a
Like you said the "update all" button behaviour can be done by selecting
and unselecting the Update checkbox. But I find it not very elegant
solution. Therefore the "extra" button makes sense to me.
Besides, it would be nice if, in the future, the "update all" button become
"updated selected itens
On 2015-10-14 12:12, Sandro Santilli wrote:
On Wed, Oct 14, 2015 at 11:53:14AM +0200, Bas Couwenberg wrote:
On 2015-10-14 11:35, Sandro Santilli wrote:
>And, would it be ok for it to not be an LTR before Feb 2017 ?
For Debian that's probably too late, the freeze in preparation for
the stretch s
On Wed, Oct 14, 2015 at 11:53:14AM +0200, Bas Couwenberg wrote:
> On 2015-10-14 11:35, Sandro Santilli wrote:
> >Now the question is: when would a QT5 compatible version be needed ?
>
> A Qt5 compatible version is already needed.
>
> QGIS is one of the blockers for the Qt4 WebKit removal in Debia
On 2015-10-14 11:35, Sandro Santilli wrote:
Now the question is: when would a QT5 compatible version be needed ?
A Qt5 compatible version is already needed.
QGIS is one of the blockers for the Qt4 WebKit removal in Debian for
example (see: https://bugs.debian.org/784514).
And, would it be
On Wed, Oct 14, 2015 at 11:19:44AM +0200, Richard Duivenvoorde wrote:
> ps my personal idea:
>
> Work hard on 2.14 AND docs for it, to be the last but most stable
> 2.x
> version ever by being very carefull about what put in 2.13 (maybe a
> (big)feature freeze)
> Then after 2.14 concentrate on mov
On 14-10-15 10:44, Sandro Santilli wrote:
> Personally I wouldn't care about missing 2.12, but 2.14 LTR is what
> I'm looking at (although it is always hard for me to figure out
> exactly when it is expected, I guess Feb 2016 ?).
Oi Sandro,
plz bookmark ;-)
http://qgis.org/en/site/forusers/inde
On Wed, Oct 14, 2015 at 07:59:37AM +, m roy wrote:
>
>
> Il 14/10/2015 08.20, Paolo Cavallini ha scritto:
> > Sure. Another option, if we feel there are no compelling reasons to
> > have another LTR (I believe 2.11 have few additional function people
> > can't really miss, and 2.8 seems gen
On Wed, Oct 14, 2015 at 9:59 AM, m roy wrote:
> Il 14/10/2015 08.20, Paolo Cavallini ha scritto:
>> Sure. Another option, if we feel there are no compelling reasons to
>> have another LTR (I believe 2.11 have few additional function people
>> can't really miss, and 2.8 seems generally quite well a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
> could you provide the full stack trace?
>
> thanks!
here it is.. first the last lines of the log:
|1984.904889-1992.787789|from to . . . . . . . . . . . . . . . . .|
0.00772|
|1992.787789-2000.670689|from to . . . . . . . . . . . . . . . . .|
0.
Also +1 for the idea and the effort. Would there be a (sketchy) timeline
and a closing date for applications? May be of interest for those
considering to apply but have rather tight schedules.
Thanks & all the best
Thomas
--
___
Qgis-developer maili
Il 14/10/2015 08.20, Paolo Cavallini ha scritto:
> Sure. Another option, if we feel there are no compelling reasons to
> have another LTR (I believe 2.11 have few additional function people
> can't really miss, and 2.8 seems generally quite well accepted), to
> skip next LTR and go straight aw
could you provide the full stack trace?
thanks!
2015-10-14 9:19 GMT+02:00 Matteo Ghetta :
> Hi Victor,
> tested but I have this error:
>
> 'NoneType' object has no attribute 'value' See log for more details
>
> same error with v.report..
>
> thanks Victor!
>
> Matteo
>
> Il giorno 13/ott/2015 20.
Hi Victor,
tested but I have this error:
'NoneType' object has no attribute 'value' See log for more details
same error with v.report..
thanks Victor!
Matteo
Il giorno 13/ott/2015 20.04, "Victor Olaya" ha scritto:
> Matteo,
>
> I just pushed a fix for that
>
> Could you please test?
>
> Thank
> Isn't there another way to provide same capabilities without two buttons?
>
If i understood what bother you is the fact that there are two
options (check box and button) to do quite the same thing, to
me it's ok because i see they have different behaviour (one is fully
automatic).
If this both
45 matches
Mail list logo
