You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a Windows environment (and possibly others), doing a find-and-replace operation, after either accepting or canceling the proposed replacements, Komodo IDE is no longer the active application, and instead focus is passed to whichever application was being used prior to Komodo IDE.
Steps to Reproduce
Edit > Replace. Enter any strings into the "Find" and "Replace" fields such that at least one possible replacement will be found. In the "Where" field, choose "Files". Start the process (I do that by pressing Enter, but there might be some other favored technique).
Expected Results
When Komodo IDE has finished finding and making all of the possible replacements -- or even before it has finished and you click the "Cancel" button -- focus should return to the main Komodo IDE window as soon as the replacement dialog disappears.
Actual Results
Instead focus is passed to whichever other running application was accessed prior to switching to or starting Komodo IDE. Komodo IDE becomes the next-in-line application. In effect, Komodo IDE and the other application switch places in the activity queue (or whatever it is that Microsoft calls the order in which applications are accessed when going from one to another using Alt+Tab).
Platform Information
Komodo IDE 10.2.3 on Windows 10 Pro
The text was updated successfully, but these errors were encountered:
With Windows 10 64bit with Komodo 11.0.2:
Can't repro the change of focus exactly as described above, but there is definitely something weird happening, and it can be seen with just the Find tool.
When you get to the end of a set of matches, the Linux version returns to the top of the set of matches.
On Windows, you get two different (wrong?) results.
If you're stepping with the F3 key, after the last match you return to your current cursor position in the active file.
If you're stepping with the Up/Down arrows in the Find box, after the last match you're returned to the Find box Find: field where you set your search keyword. This isn't quite the same as what was reported, but it's still an unexpected shift of focus.
Thanks for the feedback. Because we have upgraded to Komodo IDE 11 since my original post, just now I verified the misbehavior described in that post, in my current Komodo IDE 11.0.2 build 90813 (on Windows 10.0.16299.192 Pro), after doing Help > Troubleshooting > Restart in Safe-Mode.
I confirm the original report as written. It seems the find in files dialog takes focus away from Komodo, and after dismissing the dialog, focus is given to another open window other than Komodo.
Summary
In a Windows environment (and possibly others), doing a find-and-replace operation, after either accepting or canceling the proposed replacements, Komodo IDE is no longer the active application, and instead focus is passed to whichever application was being used prior to Komodo IDE.
Steps to Reproduce
Edit > Replace. Enter any strings into the "Find" and "Replace" fields such that at least one possible replacement will be found. In the "Where" field, choose "Files". Start the process (I do that by pressing Enter, but there might be some other favored technique).
Expected Results
When Komodo IDE has finished finding and making all of the possible replacements -- or even before it has finished and you click the "Cancel" button -- focus should return to the main Komodo IDE window as soon as the replacement dialog disappears.
Actual Results
Instead focus is passed to whichever other running application was accessed prior to switching to or starting Komodo IDE. Komodo IDE becomes the next-in-line application. In effect, Komodo IDE and the other application switch places in the activity queue (or whatever it is that Microsoft calls the order in which applications are accessed when going from one to another using Alt+Tab).
Platform Information
Komodo IDE 10.2.3 on Windows 10 Pro
The text was updated successfully, but these errors were encountered: