9 Mar
2025
9 Mar
'25
6:50 a.m.
Hi,
does someone know why tdepowersave is not working with dcop or kdcop
I am trying to change the scheme via dcop but get false and no change
$ dcop tdepowersave tdepowersaveIface currentScheme
Powersave
$ dcop tdepowersave tdepowersaveIface do_setScheme Presentation
false
$ dcop tdepowersave tdepowersaveIface currentScheme
Powersave
but it is possible to change the scheme via the applet in the taskbar
thanks
--
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
9 Mar
9 Mar
5:06 p.m.
deloptes via tde-devels wrote:
Hi,
does someone know why tdepowersave is not working with dcop or kdcop
I am trying to change the scheme via dcop but get false and no change
$ dcop tdepowersave tdepowersaveIface currentScheme
Powersave
$ dcop tdepowersave tdepowersaveIface do_setScheme Presentation
false
$ dcop tdepowersave tdepowersaveIface currentScheme
Powersave
but it is possible to change the scheme via the applet in the taskbar
thanks
Do you know why it is commented in the code? (line 2738 tdepowersave.cpp)
/*!
* DCOP Interface funtion to set the current scheme.
* \return boolean with the result of set the requested scheme
* \retval false if failed (e.g. scheme is not in the list)
* \retval true if scheme found and set
* \param _scheme TQString with the scheme to set, scheme should be
* named as list from list_schemes()
*/
bool tdepowersave::do_setScheme( TQString /*_scheme*/ ) {
kdDebugFuncIn(trace);
/* int index;
index = settings->schemes.findIndex(_scheme);
if (index != -1) {
do_setActiveScheme(index);
kdDebugFuncOut(trace);
return true;
}
else {
kdDebugFuncOut(trace);
return false;
}
*/
kdDebugFuncOut(trace);
return false;
}
--
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
12:32 a.m.
Michele Calgaro via tde-devels wrote:
Hi Emanoil,
it seems to have been commented out from the very beginning. Perhaps you
can test it out and if it works fine, create a PR to reenable the code?
Hi Michele,
thanks for the reply.
Yes, also found out and tested and it is working.
I will test the same for the CPU policy as it is also commented out and will
create a PR for both.
BR
--
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
12:45 a.m.
On 2025/03/10 09:32 AM, deloptes via tde-devels wrote:
Michele Calgaro via tde-devels wrote:
Sounds good, thanks for the effort :-)
Cheers
Michele
Hi Emanoil,
it seems to have been commented out from the very beginning. Perhaps you
can test it out and if it works fine, create a PR to reenable the code?
Hi Michele,
thanks for the reply.
Yes, also found out and tested and it is working.
I will test the same for the CPU policy as it is also commented out and will
create a PR for both.
BR
6:36 a.m.
Michele Calgaro via tde-devels wrote:
Sounds good, thanks for the effort :-)
no
problem - my pleasure.
in fact it seems we could use the tdepowersave for the dbus screen saver
task much easier by assigning the proper scheme (performance or powersave
vs presentation)
1. it handles the screen saver
2. it handles the DPMS
3. it is configurable
But as you said - we do step by step
I see you are busy with some other tasks and I am also.
BR
--
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
24
days inactive
25
days old
5 comments
2 participants
participants (2)
-
deloptes -
Michele Calgaro