On Fri, Jul 20, 2012 at 11:59 AM, Jürgen E. wrote:
> Hi Etienne,
>
> On Thu, 19. Jul 2012 at 19:16:03 -0300, Etienne Tourigny wrote:
>> I guess then the pragmatic way to resolve these kinds of issues is to spawn
>> them in working threads and implement mechanisms for cancelling it. Is this
>> pos
> - Identify tool in a *very* large vector layer
this issue is really hurting, because does not affect just very large
vectors, but also small vectors with very complex (lot of nodes)
features.
http://hub.qgis.org/issues/4819
The ticket has a patch attached and would be nice is someone of the c
Hi Etienne,
On Thu, 19. Jul 2012 at 19:16:03 -0300, Etienne Tourigny wrote:
> I guess then the pragmatic way to resolve these kinds of issues is to spawn
> them in working threads and implement mechanisms for cancelling it. Is this
> possible with the current api?
I don't think so - the provider
Hi Etienne
On Fri, Jul 20, 2012 at 12:16 AM, Etienne Tourigny
wrote:
>
> I guess then the pragmatic way to resolve these kinds of issues is to
> spawn them in working threads and implement mechanisms for cancelling
> it.
> Is this possible with the current api?
Well, there is generic Qt API - e.
Hi,
On Thu, Jul 19, 2012 at 5:45 PM, Jürgen E. wrote:
> Hi Etienne,
>
> On Thu, 19. Jul 2012 at 15:17:42 -0300, Etienne Tourigny wrote:
>> A more generic question - is there a way that we could implement a
>> generic mechanism for stopping a processing that takes forever, such
>> as
>>
>> - Ident
Hi Etienne,
On Thu, 19. Jul 2012 at 15:17:42 -0300, Etienne Tourigny wrote:
> A more generic question - is there a way that we could implement a
> generic mechanism for stopping a processing that takes forever, such
> as
>
> - Identify tool in a *very* large vector layer
> - unresponsive WMS serv
A more generic question - is there a way that we could implement a
generic mechanism for stopping a processing that takes forever, such
as
- Identify tool in a *very* large vector layer
- unresponsive WMS server (when opened in the browser dock)
I would like to be able to be able to cancel such a
Hi Bernhard,
On Thu, 19. Jul 2012 at 11:22:32 +0200, Bernhard Ströbl wrote:
>> The detection is now done in a thread, so you can cancel the detection.
> also as a user - how?
The "Connect" button turns to "Cancel" (or "Stop"?) - just click on that. It
will then stop when the last running query
