Bug 327673

Summary: Usability: sensor browser can be hard to find later after collapsing it completely
Product: [Unmaintained] ksysguard Reporter: Travis Evans <travisgevans>
Component: generalAssignee: KSysGuard Developers <ksysguard-bugs>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: cfeck, richard.llom
Priority: NOR    
Version First Reported In: 4.11.3   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Travis Evans 2013-11-16 02:04:38 UTC 
Many months ago I set up a ksysguard window with all the tabs and sensors I wanted. I then collapsed the sensor browser to get it out of the way.

Today, I wanted to make changes. I no longer remembered how I hid the browser. There was no visual indication anywhere on the window that the browser even existed. There was nothing on the menus to bring it back. It wasn't until my mouse finally happened to move over the very right side of the window and changed to the double-arrow—that's where the browser panel was. But with the window style I was using there was *no* visible gripper or anything that would have made it obvious that the pane was there.

The invisibility may be the fault of the widget style and not ksysguard. However, I would suggest putting the sensor browser on the View menu so that it can be toggled on and off, and turning it back on automatically restores it to a default size if the pane is currently set at 0 width.

Reproducible: Always

Steps to Reproduce:
N/A
Actual Results:  
N/A

Expected Results:  
N/A
Comment 1 Christoph Feck 2013-11-16 12:57:01 UTC 
That would indeed be an issue with all splitters that allow collapsing one half completely. Maybe the sensor browser should be a dock, not a splitter. Btw, which style do you use? Oxygen at least has some pair of dots for the splitter.
Comment 2 Travis Evans 2013-11-18 12:26:07 UTC 
Looks like I'm currently using Oxygen. I do see the dots now (along with the mouseover highlight)—but on my screen the dots are tiny and barely visible [my extreme nearsightedness probably doesn't help, either :-) ]
Comment 3 Richard Llom 2019-03-12 18:46:42 UTC 

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