| Re: Re: Non-Panel version
Oct 20 2015 on content Take a break |
Hi again
I agree on RSIBreak being a little complicated on options and also think your idea of a small and non-intrusive plasmoid is very good. Was only mentioning it as an inspiration of ideas for your plasmoid as they share purposes. But looks like you knew it anyway.
About the panel vs. non-panel, yes I agree that with maximized windows the plasmoid is meant to be put in the panel. The problem with the panel is that it gets crowded fast with all the plasmoids one uses. I thus like using the desktop sometimes for plasmoids that do not need to always be "in sight" and need my attention.
As far as I remember from plasma 4 it was only a small change in the code to accommodate for panel vs. desktop format for a plasmoid but do not know how it is with plasma 5. Usually though most plasmoids come with the option to work on both. So I was thinking it is just a small change away to make it work also on the desktop but if that is no priority for you I might have a look into it myself ;). So no pressure there.
Now I got another idea but that might be even more complicated to implement ;). The plasmoid could be part of the system tray and thus be only shown when active, i.e. when a break is needed, and be hidden the rest of the time. But like I said, that might be even more difficult to implement, so maybe something for the nice to have future.
Thanks for the work
Hookahey |
|  | | Non-Panel version
Oct 19 2015 on content Take a break |
Hi
Nice and useful plasmoid. If you want to go further on ideas and options for it, then have a look at RSIBreak https://userbase.kde.org/RSIBreak
Why I am posting though is to ask that why the plasmoid does not seem to work outside of the panel, i.e. when added to the desktop. It does not show the time when on the desktop. Is it on purpose panel-only? Would be nice to let people choose where to put it.
Thanks
Hookahey |
| | | Re: How it works?
Feb 9 2013 on content Windows Wall |
Hi
Well KDE makes it a bit difficult to find and activate I have to admit but from KDE 4.10 on there is a GHNS button which is only a icon of a "favorites star" without text. You can find it under System Settings -> Window Behavior -> Task Switcher under Visualization. There is a drop down list of the various installed Window Switchers and next to it the GHNS star button.
Anyway if you have installed it through plasmapkg it should appear there, too.
The confusion is that these switcher scripts won't appear under effects or kwin scripts but only under Task Switchers. After installing it you will find Windows Wall in the drop down list there. |
| | | Re: Re: Re: Re: Bug with Redshift
Jun 28 2011 on content Flux / Redshift Plasmoid |
Hi. You can for example set the gamma values to 0.0 and then redshift will not start as it needs the values between 0.1 and 10 I think. But anyways, it might be difficult to always keep pace with the expected values of both programs and the various versions that users might have installed. So before you try to prevent every possible config mistake it is easier to detect program launch errors and thus get the bug reports from users ;) or some people would then at least know what they set wrong and correct it themselves.
Bye
Hookahey |
| | | Re: Re: Bug with Redshift
Jun 26 2011 on content Flux / Redshift Plasmoid |
Thanks for the fast reaction. Now it seems to work. Nevertheless, it would be beneficial to test the return code of the program you started to see if something went wrong and maybe show the error message. This would help users if they input wrong values in the config dialog and the program won't start anymore because of that. At the moment it just fails silently.
Bye
Hookahey |
| | | Bug with Redshift
Jun 23 2011 on content Flux / Redshift Plasmoid |
Hi
With Redshift version 1.6 your plasmoid fails to start it. The bug seems to be how redshift expects the gamma argument. Thus when you try to start redshift from your plasmoid it just complains about a wrong argument and won't start.
It seems you pass the gamma value as a float where redshift expects a value for each of RGB (see redshift -h).
Bye
Hookahey |
| | | Feature addition
Mar 24 2011 on content Simple CPU Sensor |
Hi
I added a small feature to the plasmoid. It adds an inertial momentum to the temperature change. My CPU temperature oscillates between two values when idle (50-51°) and it is rather distracting to see the plasmoid reflect these changes. Now it will only display a change if there is a bigger difference (3°).
This code snippet should be added to the init() function:
Quote:
...
self.resetTimer = QtCore.QTimer()
self.resetTimer.setInterval(30000)
self.resetTimer.start()
QtCore.QObject.connect(self.resetTimer, QtCore.SIGNAL("timeout()"), self.resetOldTemp)
self.resetOldTemp()
self.timer = QtCore.QTimer()
self.timer.setInterval(2000)
self.timer.start()
QtCore.QObject.connect(self.timer, QtCore.SIGNAL("timeout()"), self.updateLabel)
self.updateLabel()
Also add the following snippet after the retrieval of the temperature in updateLabel():
Quote:
...
if (abs(t - self.oldTemp) > 3):
self.oldTemp = t
else:
t = self.oldTemp
...
and before setting the label text. One would have to experiment a bit with the threshold value but 3° seems to produce good results. The second timer used above is there to force showing the real temperature value if for a longer time (30s) there was no change otherwise the shown value can be off by +-2 and stay there. That's what the function below is needed for:
Quote:
def resetOldTemp(self):
self.oldTemp = 0
Bye
Hookahey
|
| | | Feature addition
Mar 24 2011 on content Simple CPU Sensor |
Hi
I added a small feature to the plasmoid. It adds an inertial momentum to the temperature change. My CPU temperature oscillates between two values when idle (50-51°) and it is rather distracting to see the plasmoid reflect these changes. Now it will only display a change if there is a bigger difference (3°).
This code snippet should be added to the init() function:
Quote:
...
self.resetTimer = QtCore.QTimer()
self.resetTimer.setInterval(30000)
self.resetTimer.start()
QtCore.QObject.connect(self.resetTimer, QtCore.SIGNAL("timeout()"), self.resetOldTemp)
self.resetOldTemp()
self.timer = QtCore.QTimer()
self.timer.setInterval(2000)
self.timer.start()
QtCore.QObject.connect(self.timer, QtCore.SIGNAL("timeout()"), self.updateLabel)
self.updateLabel()
Also add the following snippet after the retrieval of the temperature in updateLabel():
Quote:
...
if (abs(t - self.oldTemp) > 3):
self.oldTemp = t
else:
t = self.oldTemp
...
and before setting the label text. One would have to experiment a bit with the threshold value but 3° seems to produce good results. The second timer used above is there to force showing the real temperature value if for a longer time (30s) there was no change otherwise the shown value can be off by +-2 and stay there. That's what the function below is needed for:
Quote:
def resetOldTemp(self):
self.oldTemp = 0
Bye
Hookahey
|
| |
Search people
Current visitors
New users
Birthdays
Most active users
Back
|
|
