Bug 478292 - Search almost unusable with multiple files open
Summary: Search almost unusable with multiple files open
Status: RESOLVED DUPLICATE of bug 468703
Alias: None
Product: kdevelop
Classification: Applications
Component: UI: general (show other bugs)
Version: 5.12.230803
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-09 07:25 UTC by Aaron Williams
Modified: 2023-12-09 12:13 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Screen shot showing it screwing up when I hit F3. Note that I was editing in the 3rd window but it is searching in the 1st (left) window. Both are the same file. It is also searching the wrong word. (49.48 KB, image/png)
2023-12-09 07:25 UTC, Aaron Williams
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Williams 2023-12-09 07:25:08 UTC
Created attachment 164031 [details]
Screen shot showing it screwing up when I hit F3. Note that I was editing in the 3rd window but it is searching in the 1st (left) window. Both are the same file. It is also searching the wrong word.

SUMMARY
I have four files open side-by-side in Kdevelop and in one of the editors I type ^F then type what I want to search for and the search happens in a different editor context, the only way I can search in the window I want to search is to click the mouse on the proper window afterwards and press F3. It keeps trying to search the wrong file. What is even more infuriating is it will often search a previous search term, not the one that is in the Find dialog. For example, I'm searching for "Product ID" in the 3rd of 4 windows but it is searching for "create" when I hit F3 in the first window even though it shows Product ID in the Find dialog.

STEPS TO REPRODUCE
1. Open multiple files (or even the same file) in multiple editor contests
2. Select a particular file/editor window
3. Type ^F
4. Type in the text to search
5. Watch it search the wrong context as it jumps to a different context than the one that was being edited

OBSERVED RESULT
Often when I do this it does not search the editor context that was active but will jump to a different file/context and search that window instead.
When this happens, it will happen consistently, always jumping to the same window. The only way to search the correct window is to then click on the proper window and press F3. Even with F3, it will sometimes jump back to the wrong window.

This doesn't happen every time, and in fact it may not happen for quite a while, but when it does it will consistently jump to the wrong window to search rather than the one that was being edited.

EXPECTED RESULT
I expect search to always occur in the currently selected window.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
In the current case where it is happening, I have four windows. From left to right, the first window is a Python file, the 2nd is a YAML file, the 3rd is the same Python file, and the 4th is a Makefile. I am trying to search in the 3rd window but it keeps searching the 1st window instead.
Comment 1 Aaron Williams 2023-12-09 07:49:13 UTC
I have some more info on the searching for the wrong term. When I go to search, it jumps to a different window and searches the last item I searched for in that window, not the current search term in the current window. To do what I want it to do I have to then click on the current window I was using then hit F3.
Comment 2 Aaron Williams 2023-12-09 07:54:20 UTC
Another observation is it seems to jump to the previously active window, not the currently active window. For example, if I'm editing in window 3 but previously was editing in window 2, it will search window 2 for the last search term used in window 2 rather than the current search term in window 3.
Comment 3 Igor Kushnir 2023-12-09 12:13:29 UTC

*** This bug has been marked as a duplicate of bug 468703 ***