Hi all !
The ThreadSearch plugin main idea is to be able to continue viewing/editing code during a text search (being blocked for 5 minutes is boring and I experienced that too many times). That's why I started this plugin.
I chose to use this graphical control for 3 reasons :
- quite the same strategy as in the 'Search in files'
- allows being consistent with C::B standard search options (case, whole words, beginning of words, reg ex...)
- all is managed by the control, you just have to provide informations and you don't reinvent the wheel.
Nevertheless, I agree that mixing gui calls in the worker thread may be surprising if reasons are not know.
I'll may have a look at Scintilla code to see if it is possible to extract search algorythm quite easily.
But I am very frustrated not understanding why this code does not work.
Concerning the proposed doors :
I tried Door one but I can't find the exit
I am not a fan of door 2 because this plugin looses part of its interest and may be more unpleasant to user.
The third looks the good one but requires more efforts... I'll probably choose this one but I have to improve my knowledge about wxScintilla and wxString possibilities.
Dje