Closed icecube45 closed 2 years ago
lgtm, i feel like the arbiter might not be the best place for it.. but ill reserve my judgment until i ever have to use it haha (and then just refactor then)
lgtm, i feel like the arbiter might not be the best place for it.. but ill reserve my judgment until i ever have to use it haha (and then just refactor then)
I think it's the best place (right now) because arbiter is already shoved into everything that I'd want to inject button presses (media page, plugins)
but with some exploratory work I'm doing in aasdk/openauto regarding media / navigation services, I'm thinking I might end up writing an extended openauto interface that handles this / callbacks and such. That's in the future though.
yeah I would think you would still be using the arbiter, but you could instead just access the openauto stuff via arbiter->layout()->openauto_page
(basically a direct call vs using the signal/slot stuff)
but that openauto interface would actually be awesome! could add that to the Session object so that way it can be accessed from anywhere, and that way we can refactor out all the current openauto "interface" stuff from the page (which should really just be UI stuff anyway)
Adds method into arbiter that can inject button presses into OpenAuto (this means we can now play/pause/whatever from within dash and plugins).
Requires https://github.com/openDsh/openauto/pull/22