New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"File In Files progress…" is always shown #293
Comments
Also, when the search is done, the Notepad++ window takes focus. I was typing something in another application, and suddenly got myself typing into Notepad++. |
Hi, I have modified the Find In Files progress that way. About the focus, I thought that it would be helpful to the user to show and focus on N++ window on Find In Files completion as a notification and automatic displaying of the results. Otherwise one would constantly need to manually check if the search is ready or not. Perhaps it is a matter of preference. Thanks for the feedback! |
Thank you for these detailed explanations :) I largely disagree… I was going to elaborate, but just a few points:
So basically, my opinions are the opposite of yours ;) Could other users provide their feedback to settle on this? |
Instead of taking focus you could flash the taskbar entry and keep keep flashing it with an interval until the user changes focus to the application requesting attention. |
I second @vlakoff request. |
I have the same issue. I have to work on multiple applications and this progress bar is on top and makes seeing the screen difficult. An option to choose the preference would be great. |
It may be an intentional behaviour but it's surely a unexpected result for the most of users (including me). I'll check myself if @pnedev is not available. |
Progress window is not "always on top" anymore.
After upgrading to 6.7.9.1 (from 6.7.8.2 which hadn't this issue), the "File In Files progress…" progress dialog is always shown, even if I switch to another application. The dialog is even visible when playing a movie fullscreen. This is quite surprising, and probably not intended.
The text was updated successfully, but these errors were encountered: