| Summary: | Search result window close | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | ce |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | bjoern.breitmeyer, markus.hauser, niko.sams |
| Priority: | NOR | Keywords: | triaged |
| Version First Reported In: | 3.9.98 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
ce
2010-05-05 18:17:13 UTC
You can, Window->Add Toolview... Couldn't that be done automatically? When doing the first search it does too. Not really, at least not without changes in how sublime works. The thing is that the user has requested to close this toolview, so the app should respect that and not re-open it automatically. When the user closes the Find in Files toolview after searching instead of just collapsing it, Find in Files is broken (yes, it can be repaired by manually re-adding the toolview). It is not obvious that the toolview must not be closed but collapsed. Executing Find in Files without seeing the actual results doesn't make any sense :D Oh, and the same issue is with all other Output Views as well. Imho we should do something about that. I know about that behavior of the program but just faced the same problem: I wanted to minify the search result but instead closed it... Maybe you should replace the close button with a minify button or just remove it, so the user clicks on the buttom at the bottom to minify the view... Just to let you know that there are more users facing this problem. *** Bug 257073 has been marked as a duplicate of this bug. *** Andreas, this is a very valid bug report. If the view was closed, the outputview should get notified of that and add a *new* view once new input comes in. Removing a toolview does not mean it should be hidden for eternity. Is this still valid? I can't seem to *close* the output view. 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 set the bug status 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! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! |