Il 08/06/2015 20:52, Richard Duivenvoorde ha scritto:
> Not sure if it is related, but some things should be fixed already:
>
> see https://hub.qgis.org/issues/10619
>
> looking into the fix, it uses a spatial selection now...
It should be on 2.8.2 then - I cannot see an effect.
Thanks for the
On 9 Jun 2015 1:07 pm, "Larry Shaffer" wrote:
>
> Hi,
>
> This can be fixed for Qt 4.8.x, but requires direct access to the Cocoa
API when needed to introduce the non-Qt-source workarounds noted in the
QTBUG-40449 [0].
>
> Btw, this is an example of my old PR [1] to introduce abstracted calls to
t
Hi,
This can be fixed for Qt 4.8.x, but requires direct access to the Cocoa API
when needed to introduce the non-Qt-source workarounds noted in the
QTBUG-40449 [0].
Btw, this is an example of my old PR [1] to introduce abstracted calls to
the OS (Mac for example, with Objective-C++) to handle cha
Hi
> On 09 Jun 2015, at 02:16, Richard Duivenvoorde wrote:
>
>
> Hi Devs,
>
> if you have some time, can you please add items at:
>
> http://changelog.qgis.org/qgis/version/2.10/
>
> so we can try to create a nice looking Visual Changelog again for Pisa?
>
> Let us know about all the niceti
Perfect! Thanks a lot, Richard!
Andreas
On 08.06.2015 21:30, Richard Duivenvoorde wrote:
On 07-06-15 11:40, Andreas Neumann wrote:
Hi,
Is it possible to filter in hub.qgis.org the recently closed issue - say
I want to list the issues that had been closed in the past 2 weeks.
Hi Andreas,
I'v
On 07-06-15 11:40, Andreas Neumann wrote:
> Hi,
>
> Is it possible to filter in hub.qgis.org the recently closed issue - say
> I want to list the issues that had been closed in the past 2 weeks.
Hi Andreas,
I've added a public query: 'Recently closed issues' which just queries
all closed issues
Hi Devs,
if you have some time, can you please add items at:
http://changelog.qgis.org/qgis/version/2.10/
so we can try to create a nice looking Visual Changelog again for Pisa?
Let us know about all the niceties you did this release :-)
Regards,
Richard Duivenvoorde
On 08-06-15 17:37, Paolo Cavallini wrote:
> Il 08/06/2015 17:35, Paolo Cavallini ha scritto:
>> Hi all,
>> loading a large table requires the loading of all records. This is a
>> real performance killer, and effectively prevents the use of layers with
>> millions of records. Not a new issue, I know
Maybe a reiteration of this thread discussed on this list as
"Struggling with iface.openFeatureForm()"?
and this issue "iface.openFeatureForm() does not update feature"
https://hub.qgis.org/issues/11099 ?
-S.
2015-06-08 19:25 GMT+02:00 Stefan Keller :
> Hi
>
> I have a layer of "Memory storage" t
Hi
I have a layer of "Memory storage" type (Memory provider) which I
created with Python.
When editing=on and updating values using the attribute table
interactively everything works as expected, i.e. the record get's
updated.
Then I'm checking "Auto open form" to on.
Now, when updating the object
In Python, is it possible to retrieve the value for an HTML map tip:
Layer Properties > Display > Map tip display text > HTML
I've been rooting around in the API, but haven't managed to find it.
Thanks
Tom
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Python-binding-f
Il 08/06/2015 17:35, Paolo Cavallini ha scritto:
> Hi all,
> loading a large table requires the loading of all records. This is a
> real performance killer, and effectively prevents the use of layers with
> millions of records. Not a new issue, I know, but: is there anyone
> working, or planning to
Hi all,
loading a large table requires the loading of all records. This is a
real performance killer, and effectively prevents the use of layers with
millions of records. Not a new issue, I know, but: is there anyone
working, or planning to, in order to improve this situation? Is there a
workaround
You can use the instance of ModelerAlgorithmProvider that is stored in
the Processing object.
Like this:
model = ModelerAlgorithm.fromFile("Path/to/your/model/file")
model.provider = Processing.modeler
Processing.modeler.algs.append(model)
That will add your model to the list of available ones
I agree - a rename to "size assistant" or "sizing assistant" would be
useful. In my opinion, the new solution is not harder to find than the
old solution - which was pretty hard to find and even more disconnected
to the actual symbol than the new solution. I agree, it is still a bit
hidden, but
Hi,
I'm working on a plugin and I need to use my own model inside.
I know how to add a new algorithm in processing but I didn't find something
on how to add a model to processing.
Is there a way to ship my model with the plugin ?
Or do I need to copy manually my model into the processing models f
Alexandre Neto wrote
> Not sure if data-defined override for Symbol Size should even be connected
> to the size-scale method, since in this case it should simply override the
> symbol size value.
In master UI refactoring, area or diameter selector disappeared, and we now
have an assistant for that
Hi Vincent,
On Mon, Jun 8, 2015 at 9:03 AM, Vincent Mora
wrote:
> Is the size-scale method set to Diameter ? If it's not the case (i.e.
> scale method area), then a square root is applied if the size is defined by
> an expression.
>
>
You are right, setting size-scale to diameter, makes it work.
On Jun 8, 2015 10:03 AM, "Vincent Mora" wrote:
>
> On 05/06/2015 16:46, Alexandre Neto wrote:
>>
>> I'm still at 2.8.1 (I have no administrator permissions on this machine)
>>
>> Using data-defined override on a marker symbol does not seem to be
working
>> as it should. Comparing a layer where the
On 05/06/2015 16:46, Alexandre Neto wrote:
> I'm still at 2.8.1 (I have no administrator permissions on this machine)
>
> Using data-defined override on a marker symbol does not seem to be working
> as it should. Comparing a layer where the marker size is set to 50 and
> another where we use 50 as
20 matches
Mail list logo
