https://bugs.kde.org/show_bug.cgi?id=378918
Bug ID: 378918
Summary: Sending QDBus suspend and resume commands don't affect
RSIBreak menu - as minor as just possible
Product: rsibreak
Version: 0.12.6
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: NOR
Component: general
Assignee: aa...@kde.org
Reporter: promike1...@gmail.com
Target Milestone: ---
I've studied the RSIBreak Handbook and I saw RSIBreak can be controlled via
QDbus messages.
I'm not an expert on QDbus commands, this might be the second time that I've
tried to use it, and since there is no specific examples I had to improvise.
Having run the 'qdbus org.kde.rsibreak /rsibreak' command, which can be read in
the handbook, I got some outputs like:
method void org.rsibreak.rsiwidget.resume()
method void org.rsibreak.rsiwidget.suspend()
After running qdbus org.kde.rsibreak /rsibreak org.rsibreak.rsiwidget.suspend,
it suspends rsibreak, no problem with that. However if I examine the menu of
RSIbreak I will still see " || Suspend RSIbreak " instead of " |> Resume
RSIbreak "
Of course if I click on that it will change to Resume RSIbreak then I can
resume it or by simply running the command qdbus org.kde.rsibreak /rsibreak
org.rsibreak.rsiwidget.resume revokes the suspension.
I'm not sure if I use the commands correctly. In case I don't, the handbook
should be expanded by some examples. However it is a very minor bug, it doesn't
really affect RSIbreak's functionality.
I don't wish to file an other bug report since it's connected to this but if I
suspend RSIbreak when it says "Please relax for x seconds/minutes", the
notification just hangs there. I don't know if it's a bug or a feature but I
think it shouldn't be there then.
Keep up the good work!
--
You are receiving this mail because:
You are watching all bug changes.
