> > > So do you think it makes sense to have the function return some form or
> > > error instead of just returning 0, or is there a good reason it is not
> > > doing that already?
> I don't think it helps with a lot, you need to change clients to
> handle the error, at which point we've not
>
> Yes, I meant that progress bar.
> I've had that 1s idle timer idea as well, unfortunately after writing this,
> but thank you for confirming that this would indeed work.
> I will give that a try and if I can get RSIBreak to a working state on
> wayland submit a PR for it.
Excellent, thank
> I agree, if we can't make the KIdleTime framework work in Wayland there
> should be a way to query the framework if it's going to work or not.
Just to make sure that's not misread by others; the framework works
for the majority of methods used in the common case, just not this one
polling
El dissabte, 14 de novembre de 2020, a les 12:46:41 CET, Dominik Waurenschk va
escriure:
> Hi, I just came across the issue that RSIBreak is unable to count down in
> wayland, after 1 second it always resets its timer.
>
> I investigated the code and found that it calls KIdleTime, which in turn
BUILD SUCCESS
Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/325/
Project:
kf5-qt5 FreeBSDQt5.15
Date of build:
Sun, 15 Nov 2020 20:12:27 +
Build duration:
4 min 58 sec and counting
JUnit Tests
Name:
BUILD UNSTABLE
Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/324/
Project:
kf5-qt5 FreeBSDQt5.15
Date of build:
Sun, 15 Nov 2020 20:02:58 +
Build duration:
9 min 25 sec and counting
JUnit Tests
Name:
