[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    [Bug 244424] Search should not be executed in UI-Thread
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2010-08-17 4:56:09
Message-ID: 20100817045609.849636183F () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=244424





--- Comment #5 from Andreas Pakulat <apaku gmx de>  2010-08-17 06:56:08 ---
I'd suggest to not do the 'run the eventloop for short times during searching'
as this often enough causes more headaches than is useful. The reason is that
usually the code then expects its running through once and in the middle doing
some event-processing, but suddenly there's also a chance the search-code is
re-entered... So its better to write it from the start such that it can be
re-entered as Christoph said doing the search in batches. Maybe the blocks that
kate splits the document into would be easily usable for this, i.e. search in
one block, schedule a single-shot-timer to search the next block etc....

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]