New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add persistence storage #1149
Add persistence storage #1149
Conversation
Well, it depends on how the buttons report, I only monitor hardware events that trigger |
I wonder what happened to this branch?... It's been a while since it was last updated. |
Error with e.g. Kraken Ultimate: (see #1266, polychromatic/polychromatic#287) import openrazer.client as rclient
device = rclient.DeviceManager().devices[0] # First device
device.fx.breath_single(255,255,255)
device.fx.breath_dual(255,255,255, 128,128,128)
device.fx.breath_triple(255,255,255, 128,128,128, 255,255,255)
device.fx.breath_dual(255,255,255, 128,128,128) # Error happens
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I pulled this commit and tested, and was successfully able to resolve #1266
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Would we be able to get this PR merged into master? |
85068af
to
6cc3abf
Compare
This patch adds several D-Bus methods for accessing the current state of the devices (plus pylib API for the new functionality): * get*Effect * get*EffectColors * get*EffectSpeed * get*WaveDir * restoreLastEffect The star means e.g. getEffect, getLogoEffect, getScrollEffect, etc. The last one can be used to reset to the previous effect after setting a custom effect (which won't be persisted). Co-authored-by: Luke Horwell <code@horwell.me> Co-authored-by: Luca Weiss <luca@z3ntu.xyz>
6cc3abf
to
03df9f3
Compare
It's #888 plus some finishing touches. All tasks have been completed and it's working well - ready for a final review.
There are no open issues to close on this repository - the mentioned open issues are for front-ends.
Worth mentioning in the release notes: