-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
[Feature Request]: Touch/Swipe Controls for D-Pad Actions #378
Comments
Greetigns @electroflame! You're right, I think it's time to take a serious look at this again. I'm also looking into button hold detection right now as well - both topics come up on a regular basis. |
@PRProd Sounds great, thanks for taking a look! |
Any updates around this @PRProd ? I was about to install https://github.com/Nerwyn/android-tv-card but thought i'd see if there was anything happening in firemote around touchpad. |
Sorry, not yet. I was working on getting the "hold" action figured out first, and I'm not ready to release that quite yet. I found too many ways that it won't work which has been pushing back the date for a beta release. Then I went on vacation for two weeks ~ just got back to my computer today. I hope to first achieve success with the hold action, and then with your request, so I'd like to keep this issue open for now. I'll be sure to post any progress updates here. -Doug |
Hi @PRProd, Love your work with this integration! The only bit I'm missing is the ability to hold/long press, just wondering if there was any updates on getting this working? Thanks again for your brilliant work :) |
As an update for all of you ~ The past few months have been busy, and my health hasn't been the greatest, so it's taking a lot longer to get the first "button hold" beta version ready than I wanted it to. A great deal of the code that makes Firemote function has to be refactored, so the process is time consuming and a bit tedious. So far, I've "roughed in" 24 out of about 50 base buttons. I am making progress, it's just slow. Thanks for your patience. I REALLY HOPE to have a beta ready soon! -Doug |
Hooray! (that took forever) I just published official long press support in Firemote version v4.0.0! Hopefully there won't be too many issues to solve after everyone tries it out, and then I can move on to looking at this swipe thing again! slow progress is still progress, right? |
Testing on my firecube, when I press and hold it just sends multiple keypresses. (ie when I press and hold the tv responds as if I tapped over and over instead of holding) I noticed the error "Compromised with a simulated repeat press of the button" but I don't see Firecube as the list of affected devices. Using v4.0.0 Its not a big deal for me, but I do want to help contribute with reporting/testing if I can. Cheers |
Is your feature request related to a problem?
I saw that something similar was closed in #281 (mainly for not being possible), however I do think this might actually be doable using touch inputs.
Feature Request
Being able to swipe for the D-Pad actions, especially on the Apple TV remotes, is really nice for controlling things coming from the real, physical remotes.
Taps are still fine, but ideally it should be optional to swipe in a direction as well -- it doesn't need to have tracking (i.e. small vs large swipes, pausing mid-swipe, etc.) but any directional swipe should probably trigger the corresponding D-Pad action, so it's easier for users to use intuitively if they're used to swiping on their regular remotes.
Additional Comments (optional)
I saw a similar request in #281, however there was no information about how that might be accomplished. Looking around, it might be possible to simulate the touch controls using touch events and manually firing the D-Pad key events.
See:
https://github.com/iablon/HomeAssistant-Touchpad-Card
https://github.com/usernein/tv-card/ (specifically around here: https://github.com/usernein/tv-card/blob/master/tv-card.js#L194)
These do work, they're just not as polished as Firemote. Being able to swipe would really polish up the Apple remote integration, as it'd be a pretty close 1-to-1 replication of the physical remote's behavior.
The text was updated successfully, but these errors were encountered: