Invoke a panel (on layer 3) with a button
KISS Desktop Shell on KDE libs & some applications
Status: Beta
Brought to you by:
baghira-style
Menu
▾
▴
And yet again, here i am with another unusual request :D
I'm wondering if it's possible to invoke a panel set to auto hide with a button, maybe using "qdbus (something)" as command?
I know, prolly a stupid question, but it seems i'm the kind of guy who handles idiotic ideas.
Last edit: Hombremaledicto 2012-11-22
No response...Ok, i suppose it's impossible to do, then.
errr... more like a bug in sf.net? i just got the first notice on this shrug
is not but should and will be through dbus.
i've some layer 3 (and touch) related patches pending anyway and in this adeed a dbus hook for this as well =)
I was holding them back waiting for intel (from lars ;-) on other patches blocking them, but now have - expect commit during this week.
In general if i don't react on direct questions within 5 day, don't hesitate to "Bump" me (while i really didn't get this one, some may also just drop off the table)
Thank you very much =)
Then i'll wait (to be honest, i cannot wait for the upcoming goodies now that you told me!)
Oh...for the notifications: don't worry. Actually i've been afraid that i was pushing too far with my propositions.
Little off topic: i was wondering what to do for monitoring GPU and cpu temperatures. Some friends raised the issue. I think that can be done through Fifo.daemon, right?
Last edit: Hombremaledicto 2012-11-30
Just tried:
qdbus org.kde.be.shell /Shell org.kde.be.shell.showPanel FeedPanel
That's great! :D
Thank you man!
Last edit: Hombremaledicto 2012-11-30
Pro tip:
qdbus org.kde.be.shell /Shell showPanel FeedPanel
as long as the object member is sufficiently unique and matching, you can omit the domain.
Since i'm ultra lazy, it will always be like that =)
" Little off topic: i was wondering what to do for monitoring GPU and cpu temperatures. Some friends raised the issue. I think that can be done through Fifo.daemon, right?
I guess i should add the script i use? =)
Temperatures are known to "sensors", nvidia prints them by "nvidia-settings -tq GPUCoreTemp"
A FIFO is however not necessary in this case.
FIFOs are very useful to pipe a constant data stream into a label, like when you redirect the output of "tail -f /var/log/everything.log" into one you every now and then automagically get a new line appended (whenever the log updates) or if you want to utilize "top -b" (the batchmode) because the output of "top -bn1" is junk (top needs a short time to calculate reasonable average load. at the time you run "top" you can expect "top" to be on the top of the list ;-) so you need to run it infintely yet get it's output somehow into be.shell. FIFO helps =)
However sensors is not of that kind. You rather poll the current temperatures every now and then (like every 5 seconds or so) and want to display the output, so as you have to trigger the commands periodically anyway, there's no reason to not utilize the functioanlity built into be.shell to do that (the processes run asynchronous, so no matter how long they ultimately take, be.shell isn't blocked by that but of course for the time to parse the output what could be a couple of nanoseconds ;-)
qdbus org.kde.be.shell /Shell showPanel FeedPanel
Thanks, i'm ultra-lazy too!
That will save me a lot of typing while trying commands in terminal.
So, it wasn't the proper idea to use the Fifo for sensors -glad i asked before to try :D
Uploading your scripts would save me a lot of time and disasters...
Honestly, i'm a beginner, far eons from your level - btw your scripts are interesting study material.
EDIT: Thanks for the script :D
Last edit: Hombremaledicto 2012-12-07