-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Implementation of vialrgb #47
base: main
Are you sure you want to change the base?
Conversation
currently working on usb-get part
TODO: test remembering vial settings
Also, there is a problem with the usage of the machine package, and don´t quite know how to fix this |
@PercyJW-2
|
Additionally, there is no need to modify go.mod for this PR. Please revert any changes made to it. If not modifying it results in any errors, please let me know. We can work together to find a solution. |
I only modified the go.mod to be able to use on my own project. For this draft I just wanted to show what I have done. To be able to merge this implementation I am fully aware that there are some cleanups necessary. I will continue to improve this implementation and then do the cleanup and open a new pull request with a cleaned up branch
…-------- Original Message --------
On 8/17/24 11:33, sago35 wrote:
Additionally, there is no need to modify go.mod for this PR. Please revert any changes made to it. If not modifying it results in any errors, please let me know. We can work together to find a solution.
—
Reply to this email directly, [view it on GitHub](#47 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AMOCQA6MWWAXRYHB46V2WH3ZR4KEZAVCNFSM6AAAAABMSMO4FOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHAYDONZSHA).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Co-authored-by: sago35 <sago35@gmail.com>
Nice, it seems like, that that did the job |
Is there anything I can do to help move this PR forward? @PercyJW-2 |
I haven't looked at this for some time, but my last problem was, that the firmware hangs when running any kind of RGB animation and I could not debug why that is the case. If you want, you could look into it.
…-------- Original Message --------
On 2/14/25 23:31, sago35 wrote:
Is there anything I can do to help move this PR forward? ***@***.***(https://github.com/PercyJW-2)
—
Reply to this email directly, [view it on GitHub](#47 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AMOCQA3NRLP34P3SZBIQBMD2PZVEPAVCNFSM6AAAAABMSMO4FOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRQGM4DMNZSGU).
You are receiving this because you were mentioned.Message ID: ***@***.***>
[sago35]sago35 left a comment [(sago35/tinygo-keyboard#47)](#47 (comment))
Is there anything I can do to help move this PR forward? ***@***.***(https://github.com/PercyJW-2)
—
Reply to this email directly, [view it on GitHub](#47 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AMOCQA3NRLP34P3SZBIQBMD2PZVEPAVCNFSM6AAAAABMSMO4FOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRQGM4DMNZSGU).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
At this point, |
I have implemented hid communication needed to control rgb via vial. I don't know if this is clean enough to merge, but I have a working keyboard implementation at this repository.
Moreover, I maybe don't have enough time to bring the implementation up to a mergable standard but still want to provide at least inspiration for a proper implementation