Hi, @coises and All,
@coises, I suppose it would be worth to add, in the documentation, that, after pressing the ▼ key, at the rightmost part of the Search++ dialog , before the options :
Hitting the F key runs the default Find All operation
Hitting the S key runs the default Selection operation
Hitting the M key runs the default Mark operation
Hitting the H key runs the default Show operation
Regarding the general problem about focusing within the plugin dialog or within the current document, I don’t bother about it. Given that I attributed the Ctrl + Shift+ N shortcut to Search++ > Search... command :
If I decide to focus on active document ( by enabling the the stepwise Find and Replace option in Settings ), I just have to do a Ctrl + Shift + N shortcut in order to focus the Search++ dialog, again
If I decide to focus the Search++ dialog ( by disabling the stepwise Find and Replace option in Settings), I see three advantages :
Firstly, we do not modify the current document by mistake, as focus is on plugin
Secondly, we can use the Alt + F and Alt + R shortcuts to realize a stepwise Search / Replacement
At any time, we can switch to current document, by using a Ctrl + N shortcut, for possible modifications. And then, go back to the plugin with the Ctrl + Shift + N shortcut
You said, in the first of of last three consecutive pôsts :
For multiple document searches, the completion message (e.g., “Found 12 matches in 7 of 9 open documents.” or “No matches found in 5 open documents.”) could include that some (or all) documents were skipped because the find string includes characters inconsistent with the documents’ encoding. Something similar could be added to Find in Files.
I agree to add these messages which give extra inormation on the current search !
On the other hand, in your previous loooong post, you said :
3-4 Would it be better to show it on the buttons and remove the ability to select an action with other than default scope as the action for a button by shift-clicking the drop-down menu? Does anyone even realize they can shift-click the drop-down menus (the only way to know is to do it by accident or read the help)?
And I answered :
Personally, I’m rather in favor of your last point. That way, we would know exactly which operation has just been performed, and it would be really helpful when pressing the Search button , at the rightmost zone of the Search++ panel — which would clearly indicate whether we’ve selected and run : a list, a selection, a mark, or just the results of a search !
I do know about using the Shift key and a click on any drop-dwon menu. However, what is your general feeling about my reply : any operation would be clearly identified and affecting a default option would not been anymore mandatory ?!
You also said in the same post :
4 Figure out how to modify Boost.regex to get rid of the dreaded “complexity” message. Make progress responsive during a search (not just between finds, as it is now: Boost.regex as built has no progress callback, so you can only estimate progress after it succeeds or fails to find a match, not while it’s working) and let the user cancel if it’s taking too long.
And I answered :
I do not think this point is essential. Check out my post at https://community.notepad-plus-plus.org/post/106252. Apparently, for certain regular expression searches, this specific message, about complexity, may appear (even though the result is correct) when the scanned file contains an average number of lines, with nice results for smaller files and an error for big files !
Did you already tried to test the regex proposed in that post and did you deduce some facts ? I didn’t even think it was possible to get a correct result while seeing a message telling you that the current search is incorrect !!
Best Regards,
guy038