I made couple searches in "normal" mode. I run my application in debug mode. I filtered "Debug view" and wanted to check something in result of searching, so in "Find/Replace in Files" view. Surprisingly this view was empty, only in combobox I had couple items related with my searched strings. So now what? I need to find one more time what I searched earlier? Why? I wonder why these views are duplicated (objects) in every mode. I think "debug mode" has its own and "normal mode" also has its own. Is not it a waste of memory? A word about similar bug. Sometime ago I met similar situation with settings of key shortcuts - I reported this as bug 354430, where in debug mode were one set of shortcuts and in normal mode different. As far as I remember I set one shortcut in normal mode and in debug it didn't work, because was set in normal mode. I don't understand this concept of working KDevelop.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Option "Find/Replace in Files" seems to work correctly in Debug mode and in Normal mode. I got results in both. Left only one thing, which confused me a bit. Namely both modes has its own results for "Find/Replace in Files". I mean if I found something in "Debug mode", then it will be only in this mode, I will don't find it in "Normal mode" (here I need to do the same search) and vice versa. Anyway I'm not sure if this is bug or a feature. KDevelop version 5.9.221170 (22.11.70) $ apt show kdevelop Package: kdevelop Version: 4:22.08.1+p22.04+tunstable+git20221012.0016-0 Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.26.80 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 5.15.0-53-generic (64-bit) Graphics Platform: X11 Graphics Processor: Mesa Intel® Xe Graphics
(In reply to Piotr Mierzwinski from comment #3) > Left only one thing, which confused me a bit. Namely both modes has its own > results for "Find/Replace in Files". I mean if I found something in "Debug > mode", then it will be only in this mode, I will don't find it in "Normal > mode" (here I need to do the same search) and vice versa. > Anyway I'm not sure if this is bug or a feature. This is a feature of multiple areas. I don't like it myself. Plus the areas (I found 6 of them while debugging the feature some time ago) are very inefficient and sometimes slow KDevelop down noticeably, as you surmised in the bug description. Unfortunately, rewriting the feature seems a very time-consuming endeavor to me. And some users may like the feature.
OK. If this is a feature, so one can consider an issue as solved. BTW this "feature". The most annoying for me was that when I changed key short cut in Debug mode, it was missing in "Normal" mode, so I needed to set it again. > And some users may like the feature. I suppose this is a per mille. Another disadvantage is unnecessary memory usage, due to needs to hold all "areas" in memory. But RAM is cheap and programmer's time expensive.