[PATCH] RunnerManager

[Jordi Polo]

>
> other than the outstanding issues you mention, there's still the issue of
> launchQuery have both sync and async behaviour depending on what
> parameters
> are used. that needs to get split in two still.
>

In the next patch it will be only async.


> > Also, the copy of the completer in searchcontext is commented and now I
> > remember why. I spend today several hours trying to figure out why
> krunner
> > will silently die (no way to debug) when typing one letter. As a result
> > there are a zillion of kDebug everywhere and commenting that line make
> it
> > works. It is not a solution, I need to know what is really happening.
>
> it's getting deleted after being copied leaving a dangling pointer.
> kaboom.
>

When is being deleted?
There must be some usage of that constructor I am not taking into account
because as I see it is only used to create localcontext, and work with them.
But the global context that is the one used by interface also, never gets
destroyed.
In fact, if d is going to be QExplicitlySharedDataPointer'd is not the same
that just let everyone use the same globalContext and kill the localContext
idea ?



-- 
Jordi Polo Carres
NLP laboratory - NAIST
http://www.bahasara.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/panel-devel/attachments/20080424/a6d2c0a1/attachment.html