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
Right now, we have a slightly messy system of different apps receiving messages from our can bus. It can be confusing, and our can id filtering doesnt really work
Desired Additional Features
I think we need to cerate a higher level wrapper upon our can interface, and something like a "notification center" could be a good implementation.
Generally, this could be something like a subscribe/post api system, where any application should "subscribe" to a certain device's notifications (or a type of message from said device), and sending can messages can be wrapped in a "post notification" api.
With this, we could abstract and correctly implement ID filtering, and have a cleaner interface to know what messages or message types an app is receiving from
Screenshots (as needed)
No response
The text was updated successfully, but these errors were encountered:
Current Features
Right now, we have a slightly messy system of different apps receiving messages from our can bus. It can be confusing, and our can id filtering doesnt really work
Desired Additional Features
I think we need to cerate a higher level wrapper upon our can interface, and something like a "notification center" could be a good implementation.
Generally, this could be something like a subscribe/post api system, where any application should "subscribe" to a certain device's notifications (or a type of message from said device), and sending can messages can be wrapped in a "post notification" api.
With this, we could abstract and correctly implement ID filtering, and have a cleaner interface to know what messages or message types an app is receiving from
Screenshots (as needed)
No response
The text was updated successfully, but these errors were encountered: