Ok - so what's the final call here? Is someone willing to make a final
decision between bumping to 4.6 and keeping support for lucid or
bumping to 4.7 and dropping lucid? (Looks like 4.8 is out of the
question at the moment).
If someone can make a call I'll update the pull request and make sure
al
Hi,
I am facing the issue too, with a very fast workstation , windows 7 OSGEO4W
64bits. Maybe Qscintilla version differ?
Régis
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Disable-Syntax-Highlighting-in-DB-Manager-tp5090912p5091938.html
Sent from the Quantum GIS - Deve
By default, I would prefer that single "normal" keys (letters and number)
would be used only to swap between tools. Anything that implies changings
the project (adding, removing, duplicating,... layers\features\nodes...)
would use other keys (del, backspace, ...) or a combination with
"Ctrl\Shift\a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 29/11/2013 09:59, Radim Blazek ha scritto:
> Customization only works for objects with objectName. objectName
> is automatically set by Qt for objects created in designer
> (compiled from .ui). For objects created programmatically it has to
> be se
Dnia piątek, 29 listopada 2013 10:18:26 Andreas Neumann pisze:
> As long as we don't have an undo option I would like to have the
> confirmation question always when removing one or more layers. It is not
> something that people do all the time, so it wouldn't be annoying.
It seems there are at l
Thanks Matthias,
I'm arriving at the same conclusion...
I thought that it's when QGIS clean up layers and providers.
Regards
Le 29/11/2013 11:28, Matthias Kuhn a écrit :
On Fre 29 Nov 2013 09:40:03 CET, rldhont wrote:
Hi Marco,
More information with valgrind :
==26940== Invalid read of si
On Fre 29 Nov 2013 09:40:03 CET, rldhont wrote:
> Hi Marco,
>
> More information with valgrind :
>
> ==26940== Invalid read of size 4
> ==26940==at 0x43EE67: QBasicAtomicInt::deref() (qatomic_x86_64.h:133)
> ==26940==by 0x43F054: QString::~QString() (in
> /home/dhont/3liz_dev/QGIS-Compil/q
On Fri, Nov 29, 2013 at 9:01 AM, Denis Rouzaud wrote:
> Hi Paolo,
>
> In your code you update the geometry in the provider.
> You should not do this since the feature is not there yet, it's still in the
> edit session (edit buffer).
>
> There is two ways to do this: either work totally in the buff
On Wed, Nov 27, 2013 at 6:40 PM, matteo wrote:
> Hi guys,
> trying to customize the qgis toolbar and menu I found something weird (maybe
> a bug)
>
> saving the customization, you have to add manually the .ini suffix to the
> file, otherwise you are not able to load it
"Save to file" is using sta
Hi Marco,
More information with valgrind :
==26940== Invalid read of size 4
==26940==at 0x43EE67: QBasicAtomicInt::deref() (qatomic_x86_64.h:133)
==26940==by 0x43F054: QString::~QString() (in
/home/dhont/3liz_dev/QGIS-Compil/qgis_rldhont/build/bin/qgis_mapserv.fcgi)
==26940==by 0x8
Hi Marco,
This is an unstable but constant bug.
If I QGIS-Server accessing 2 layers, I have the bug. If I accessing 1
layer, I don't have the bug.
It is unstable because it's not always the same bug. Sometimes it's a
'corrupted double-linked list' like when I close QGIS Desktop, the other
tim
I'm using the libgdal-dev from ubuntugis.
I'm testing QGIS under valgrind but I don't find where it comes from.
Le 28/11/2013 23:42, Etienne Tourigny a écrit :
I have the same problem, see the bug report (closed as invalid) and
add any information
It is somehow related to the gdal build, beca
Hi Paolo,
In your code you update the geometry in the provider.
You should not do this since the feature is not there yet, it's still in
the edit session (edit buffer).
There is two ways to do this: either work totally in the buffer or
totally in the provider.
There is an agreement that worki
13 matches
Mail list logo
