Connecting configChanged() explicitly was the cause of the problem
apparently (I need to test it a little bit more). In many forum I've
found that the people suggest to do this connection, maybe it's old
stuff.
Another strange thing I noticed is that when I click OK in the config
dialog it does no
On Sunday, February 5, 2012 15:16:03 Simone Gaiarin wrote:
> I call configChanged() once in the init function and then I connect it
> to the configChanged() signal.
you don't need to connect it to any signal. i'm not sure if that's the cause
of your problem, but it is unecessary in any case.
and
I call configChanged() once in the init function and then I connect it
to the configChanged() signal.
Here you can find the code:
https://github.com/simgunz/redshift-plasmoid/blob/master/contents/code/main.py
2012/2/5 Aaron J. Seigo :
> On Sunday, February 5, 2012 11:44:02 Simone Gaiarin wrote:
On Sunday, February 5, 2012 11:44:02 Simone Gaiarin wrote:
> Hi,
> I wrote a python plasmoid that needs to restart a program (redshift)
> everytime that the configuration is changed by the user (the plasmoid
> configChanged() function reacts to the signal). When the program is
> restarted the user
Hi,
I wrote a python plasmoid that needs to restart a program (redshift)
everytime that the configuration is changed by the user (the plasmoid
configChanged() function reacts to the signal). When the program is
restarted the user is aware of it, because the screen color become
white and than red ag
