On 29 May 2015 5:55 am, Larry Shaffer lar...@dakotacarto.com wrote:
Hi,
The new icons for the Layers and Browser docks look good, but now the
sizing and spacing looks awkward when compared to the main toolbars (see 0,
1 screen snaps), especially on Mac. What's the likelihood that we can
switch
Hi,
The new icons for the Layers and Browser docks look good, but now the
sizing and spacing looks awkward when compared to the main toolbars (see 0,
1 screen snaps), especially on Mac. What's the likelihood that we can
switch those over from QToolButtons to a actions on a QToolBar instead for
Larry,
As Nyall mentioned, icon size of the dock tool button will go back to 16 x
16 by default. That'll make things look the same as before.
That said, the border on the buttons (no present on other OSes) aren't very
nice. It might be worth adding a style specifically for os x to remove
those.
Hi,
I also am involved with some work that can benefit from WPS integration of
Processing, and found René-Luc's new plugin while searching today.
What would help further in my situation is to be able to export the
Processing model into a format that can be loaded as a backend process in
another
Hi Nyall,
Thanks.
Larry Shaffer
Dakota Cartography
Black Hills, South Dakota
On Thu, May 28, 2015 at 4:36 PM, Nyall Dawson nyall.daw...@gmail.com
wrote:
On 29 May 2015 5:55 am, Larry Shaffer lar...@dakotacarto.com wrote:
Hi,
The new icons for the Layers and Browser docks look good,
Hi,
Agreed as well. Very nice place and very nice people.
Tak tak for this excellent organization.
On 27/05/2015 11:45, Matteo Ghetta wrote:
Agree!
Super fantastic organization!
Thanks Lene and thanks to all the developers, documenters, testers,
participants..
Great time in Denmark!
When referencing a QgsComposerAttributeTable from a Print Composer template
like this:
composerView = composerList[0]
composition = composerView.composition()
attrtable = composition.getComposerItemById('MyComposerAttributeTable')
I get a class 'qgis._core.QgsComposerFrame' returned in
On 28 May 2015 at 21:08, Jakob Lanstorp jlanst...@gmail.com wrote:
When referencing a QgsComposerAttributeTable from a Print Composer template
like this:
composerView = composerList[0]
composition = composerView.composition()
attrtable =
Thanks for the documentation. It's working:
attrtable =
composition.getComposerItemById('MyComposerAttributeTable').multiFrame()
returns a QgsComposerAttributeTable
Jakob
-
Jakob Lanstorp
--
View this message in context:
Dear list,
QGIS crashes when discarding all changes, made in editing mode on a temporary
vector layer. I'm writing a plugin to access and modify the attribute table
while the layer is in editing mode. When starting the editing mode, I change
the attribute values for each new feature with the
Hi Christian,
Can you give some details about which version of QGIS you are using and
possibly try to find a minimal python script to reproduce this behavior?
Thank you
Matthias
On 05/28/2015 02:41 PM, Boehnke, Christian wrote:
Dear list,
QGIS crashes when discarding all changes, made
Hi Rémi,
On Thu, 28. May 2015 at 12:06:22 +0200, Rémi Cura wrote:
When making several edit on the layer, then saving the edits.
All the edits are send one by one to the database (though in the same
transaction).
That's because of the provider interface. For vector data providers
addFeatures,
In InaSAFE we actually use Jenkins with Github PR Builder plugin now for
our reference. We had some problems with Travis: There were some tests that
could take more than 10 mins and all the tests could take 50 mins and
would hit job timeout in travis for public repo. Also sometimes the job
failed
Hey Jürgen,
this doesn't explain why each operations isn't grouped.
For instance all the addFeatures are grouped into one transaction, but not
into one statement.
Cheers,
Rémi-C
2015-05-28 16:39 GMT+02:00 Jürgen E. j...@norbit.de:
Hi Rémi,
On Thu, 28. May 2015 at 12:06:22 +0200, Rémi Cura
Hi Rémi,
On Thu, 28. May 2015 at 17:07:32 +0200, Rémi Cura wrote:
this doesn't explain why each operations isn't grouped.
For instance all the addFeatures are grouped into one transaction, but not
into one statement.
addFeatures does one prepared INSERT statement.
Jürgen
--
Jürgen E.
Also thanks, from a local, for a great event at Nødebo. Lene also
instantiated the upcoming Danish QGIS user group. A round of applause
Jakob
-
Jakob Lanstorp
--
View this message in context:
16 matches
Mail list logo