-
Notifications
You must be signed in to change notification settings - Fork 146
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
Sending dynamic images in event data - no screen reaction #89
Comments
The initial handler binding for a dynamic image handler must still include an "image-data" key like a non-dynamic one does. It's used for type identification as well as a fallback image value if dynamic data is not provided with an update. I apologize if this violates the principle of least surprise, I'll try to make it clearer in the documentation. |
Adding "image-data" key indeed solved the case, but led (or, maybe, it's a coincidence) to another issue: i'm no longer able to open app settings: ...and that's more to it -- seems that old apps and app events are somehow "stuck" in the engine even after removing them, so if an event had some incorrect bind, i can't just overwrite it, i always need to bind using a new app name in order for the new handler to apply. |
I can reproduce your frontend crash. I'll file a bug internally to get it fixed in a future version. |
I know this is bringing up old issues, but I'm hitting up against this now as well. Was this resolved or was there a work around for this? |
it's possible to update the OLED dynamically, but the frontend crash was never resolved. what issue are you having? can you link to some code? |
Currently I'm just using Postman to send requests to the API. I'm sending this to "bind_game_event":
Then trying to trigger it with "game_event":
I've also been trying it with various different configurations, including the same example from the wiki. As well as with various different lengths inside image-data. So currently its started working sort of. But it'll only send the image once, then stop working. After which the keyboard will go turn off all RGB after about 12 seconds and restart the engine I assume as everything comes back on after. |
Depending on what you're using it for, you either need a new value every time you send to game_event, or add "value_optional": true, under "event": "SCREEN" when setting up the bind event, then send your game event with NO value. The issue of the RGB turning off is because you need to send a keepalive or SteelSeries will assume your app has closed. |
I'm following the guide to dynamically update the screen.
First i bind the event using game_event_binding endpoint:
Then i send the events using game_event endponit:
No signs of errors, app appears on Apps tab, but nothing happens on the screen.
Am I missing something?
The text was updated successfully, but these errors were encountered: