You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Runekit thinks it doesn't have screen capture permission but actually does, causing Lobby Timer to fail
#38
This line in instance.py makes runekit unable to run Lobby Timer in AFKWarden properly.
I realized that runekit is actually able to run Lobby Timer and reset on click, but after the popup for no screen capture permission pops up, the Lobby Timer stops resetting when I click. Which means
Runekit actually has screen capture permission, but is unable to recognize that it has the permission
screen capture actually works with Runekit, and so does Lobby Timer
the popup and raise in the reference line forcefully halt the process and prevents it from working
i.e. the function works, but its just the code thinking it doesn't, and throws an error to stop it from progressing further.
would be great if the code can be made to somehow handle the error, so that even if the code doesn't think it has screen capture permission, it'd at least not stop itself from continuing. (In my personal branch, I just disabled the exception raise and it runs perfectly. I had to manually add the screen capture permission. Obviously not the best solution, but is a proof of concept that the code actually works without the exception)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
runekit/runekit/game/quartz/instance.py
Line 169 in 8b86d85
This line in instance.py makes runekit unable to run Lobby Timer in AFKWarden properly.
I realized that runekit is actually able to run Lobby Timer and reset on click, but after the popup for no screen capture permission pops up, the Lobby Timer stops resetting when I click. Which means
raisein the reference line forcefully halt the process and prevents it from workingi.e. the function works, but its just the code thinking it doesn't, and throws an error to stop it from progressing further.
would be great if the code can be made to somehow handle the error, so that even if the code doesn't think it has screen capture permission, it'd at least not stop itself from continuing. (In my personal branch, I just disabled the exception raise and it runs perfectly. I had to manually add the screen capture permission. Obviously not the best solution, but is a proof of concept that the code actually works without the exception)
Related:
#33
All reactions