Summary: | "Remove the tool" button unintuitive | ||
---|---|---|---|
Product: | [Developer tools] kdevplatform | Reporter: | Wolfgang Bangerth <bangerth> |
Component: | sublime | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | adymo, aleixpol, kitts.mailinglists |
Priority: | NOR | ||
Version: | git master | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Wolfgang Bangerth
2011-04-03 18:29:56 UTC
I agree that removing a tab is not common enough so that we have to have the button always visible. I'm not sure we want to hide if the X is clicked, though. Changing such a functionality in a program is weird and the users who know how it works will feel weird. If it's really troublesome I'd say we can remove the button and problem gone. I would say leave the button in place but change the semantics: instead of removing the tool, make it equivalent to what happens when you click on the tab on the perimeter of the main window ("hide" the tool). As for changing the behavior: True, change is awkward, but in general I tend to think that whenever a program has some awkward behavior that is commonly agreed makes little sense, then I'm all in favor of changing it: the few users who actively use it will adapt (and I would claim that few people actively use it, because completely removing a tool is a pretty uncommon operation) while the large majority as well as all those who may learn the tool in the future will benefit from the change. W. I still think there has to be a way to remove the view. For example, i dont want the debug view in the code area and the run view in the debug area. This state is not saved as it seems and so i have to do this each time i start kdevelop. There is of course a way to do what you want: - to close the tool view, simply click on the symbol on the perimeter - to remove the tool view symbol from the perimeter, right click on it and select "Remove toolview" W. Ah yes. That should be enough. (In reply to comment #4) Agree to this solution, patch is very velcome I think this is how it works now, if that's not the case, please reopen. |