Hi,
I have noticed that I was set as tickets owner, but I am not
QGIS-GRASS maintainer. It is better to leave owner blank, so that it
is clear that nobody is working on that.
Radim
On Sun, Mar 20, 2011 at 10:10 PM, Giovanni Manghi
giovanni.man...@gmail.com wrote:
Hi all,
today I was reviewing
Il giorno dom, 20/03/2011 alle 21.10 +, Giovanni Manghi ha scritto:
This is confirmed also by Paolo who gave a course last week and pointed
me to these problems.
Confirmed; more generally, we badly need a GRASS maintainer, otherwise
problems will accumulate to the point of rendering the
Il giorno lun, 21/03/2011 alle 08.09 +0100, Radim Blazek ha scritto:
Hi,
I have noticed that I was set as tickets owner, but I am not
QGIS-GRASS maintainer. It is better to leave owner blank, so that it
is clear that nobody is working on that.
Yes, you were the maintainer long ago. Your
On Sun, 20 Mar 2011 09:39:05 -0500, William Kyngesburye wrote
... what I'm saying is that there are 2
inconsistent uses of OMIT_GEOS and OMIT_PROJ.
#ifndef OMIT_GEOS makes sense ...
#if OMIT_GEOS == 0 is the one I've been using as a guide, and is more
confusing to think about.
Hi
On Sun, 20 Mar 2011 23:58:13 +0100, Jürgen E. Fischer wrote
Fixed in r15545.
Hi Jef,
I can confirm: my own test suite runs absolutely
smooth and fast on r15546.
bye Sandro
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
On Mar 20, 2011, at 10:55 PM, John C. Tull wrote:
Here is a patch to allow that option to be set on OS X systems. It does not
get at the root concern about unavailable items being present in the gui.
I'll give it a try. I wonder if the resize issue mentioned is still present?
And speaking
This seems like a decent suggestion (frankly, it shouldn't be necessary!),
but no matter what I try/do, the generated ui_*.py file always has the
'value' property set for the progressBar. It doesn't appear to be an
option...
$ pyuic4 --version
Python User Interface Compiler 4.7.2 for Qt version
Hi Carson,
On Mon, Mar 21, 2011 at 2:37 PM, Carson Farmer carson.far...@gmail.comwrote:
... the generated ui_*.py file always has the 'value' property set for the
progressBar. It doesn't appear to be an option...
I'm pretty sure that, if you unset the value property from QtDesigner, it
I have been keeping some of my builds. The Help Menu problem developed
somewhere between r15382 and 15529.
Royce
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
Giuseppe,
I'm pretty sure that, if you unset the value property from QtDesigner, it
doesn't appear
in the .ui file and then in the generated _ui.py file.
I'm sure you're right... but I am unable to 'unset' the value property in
QtDesigner
You may also edit the .ui file by hand and remove
Oh, I wonder if it was the moving menu setup to the UI file:
http://trac.osgeo.org/qgis/changeset/15383/trunk/qgis
That would put plugin menus after the main app menus, including the Help menu.
On Mar 21, 2011, at 11:58 AM, Cline, Royce L. wrote:
I have been keeping some of my builds. The
Hi,
Tim wrote:
Mayeul we will apply this after we branch for release (probably around
1 april).
Great!
In the meantime, to test the compatibility of the symbol levels patch
with commits made since r15217, I just proposed a patch against r15538
adding symbol levels in rule-based renderer (on top
Hi All
Just a reminder that we will enter string freeze from tomorrow. I will
put in the 'whats new' strings some time today and then I am done with
string changes from my side. I'll post another note tomorrow reminding
everyone that string changes are in effect. If you are a native
english
13 matches
Mail list logo
