[Nepomuk] Re: Improving the "Stop Button"
Vishesh Handa
handa.vish at gmail.com
Wed Mar 16 14:58:55 CET 2011
This patch ( now committed ) is not that useful.
The only thing it does is sets the time elapsed when you click the "Stop
Query" button. And it removes the old code which allowed you to
automatically stop the old query if you ran a new one.
When a query finishes execution, or is closed, it automatically deletes
itself and therefore disconnects itself from all signals and slots.
I know the setting of 'd->m_currentQuery = 0' was not completely obvious.
But it did what it was supposed to. The query if it was still being executed
would have been deleted when more results were received
in slotNextResultReady()
I'll either revert this patch or fix it.
On Wed, Mar 16, 2011 at 4:37 PM, Who Knows <who828 at gmail.com> wrote:
> The previous patch affected the copyright somehow so i am sending a new
> one.
>
>
> - Smit Shah (My real name)
>
> _______________________________________________
> Nepomuk mailing list
> Nepomuk at kde.org
> https://mail.kde.org/mailman/listinfo/nepomuk
>
>
--
Vishesh Handa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/nepomuk/attachments/20110316/5d7c7302/attachment.htm
More information about the Nepomuk
mailing list