https://bugs.kde.org/show_bug.cgi?id=351175
--- Comment #28 from Duncan <1i5t5.dun...@cox.net> --- Created attachment 131708 --> https://bugs.kde.org/attachment.cgi?id=131708&action=edit panelhider script OK, the script, which I named panelhider, works well here and is ready for others to test. =:^) Final dependencies: Core and likely installed on most distros: grep sed coreutils (for mkdir) Optional but recommended (also core and likely installed): procps (for pgrep) Required and will likely need to be installed, hopefully in your distro's repo: xwininfo xdotool The cachefile is stored in the standard $XDG_CACHE_HOME location as $XDG_CACHE_HOME/panelhider.winid.cache . If $XDG_CACHE_HOME isn't set the default $HOME/.cache/ dir is used. If $HOME isn't set either, the script will complain and exit. If necessary the dir is created with the recommended 700 perms. If the cachefile (or cachedir) can't be created for whatever reason, an appropriate error is printed and the script exits. Usage: panelhider [debug] [force] [lasttry] The parameters are optional but must appear in that order if present. Thus, if debug isn't present, the first parameter is checked for force, else the second parameter is. Similarly, if force isn't present, the first (or second with debug) parameter is checked for lasttry. Simple enough to implement with shift. =:^) debug should be obvious. When run from a konsole/terminal window it'll print a lot of interesting information about the window matching process, etc, as the script runs. Hopefully that output will help me trace down any bugs people find that I missed in my own testing. force deletes the cachefile if it exists and forces a detect and repopulation of the cachefile. Note that due to the way detection works, hidden (unmapped) panels won't be detected, so if you force with panels unmapped, you'll either have to manually run xdotool map on the window manually, or killall plasmashell and restart it (which can be done from krunner or a konsole window, you don't have to quit and restart your entire plasma session), to get your panels back. lasttry is primarily for script-internal use but can be set manually as well. If you run panelhider and it can't find any panel windows to toggle, it's likely because the winIDs in the cachefile are stale, so panelhider will normally invoke itself again with force lasttry to clear the cachefile and redetect. The lasttry is there to prevent it from going into an endless reinvoke loop so in lasttry mode it won't try again. As always, don't forget to scan the script before running it since you don't presumably don't know me and for all you know I could have put harmful commands in the script. When you're satisfied it doesn't do rm -rf $HOME or the like, place it in your path and set it executable. Then test away. =:^) If you're curious you may want to run it from a konsole window with the debug parameter to see what it's doing. When you're satisfied that it's working as expected, assign a hotkey for it or set it up via some other launcher. As I said in an earlier post, I'm considering using a gkrellm click to launch it here, but I have enough other stuff on hotkeys I'm used to hotkey launching, so that's tempting as well. We'll see. If anyone's interested in running it via xdotool's behave_screen_edge and has difficulty, I can create a stub-script to launch that and instructions for adding it to your autostart, but having played around with behave_screen_edge a bit I really can't recommend it and don't believe it's worth the trouble. Maybe for people with just a single monitor, but then they'd have less reason to be interested in this script in the first place. Anyway, hope it's useful for people other than me. =:^) And I'll still try some more on the patch thing, but I still give it less than 50% chance I have the skills to pull it off, particularly with this script now as a workaround letting off the pressure. We'll see. I think that covers it. Let me know if you have questions about it. -- You are receiving this mail because: You are watching all bug changes.
