Easier control of channel up/down etc
Hey Shane, thanks for the reply on YT. Further this: "
Thanks - so glad it working for you! When you say physical buttons, you mean like keyboard or something different? This is a bit of a gap honestly. Do you mind filing an issue on the github project and we'll figure out something better than the channel.socket text file?"
I actually meant some form of guide for a Linux / Pi noob on how to set up the buttons you have on the 3d printed cable box and the display matrix,...
However.. without that set up is there a way to assign say either numbers or arrow keys to change the channels...
At the moment in testing (I am in WSL at the mo getting it set up waiting for a Pi to arrive) I need to quit out of full screen, open up another WSL instance and go to channel Socket and enter commands and save it there to flick between channels to see if they are working....
Best,
Paul
Gotcha! Yes - it was my intention to have that done before I uploaded the video, but I will add a complete guide to that over on the cable box repo. I'll note here when that makes progress.
I mostly develop on WSL, and use the same approach as you currently. The problem with using keyboard or numbers is that something would have to have focus. Maybe a little window with some widget that could run in debug mode would work? I've also thought about a web interface controller.
Okay - I added instructions and wiring diagrams to the README over on the cable-box repo: https://github.com/shane-mason/cable-box
I still need to add how to setup the software on it - will do that shortly.
Okay - I think the documentation over on the cable-box repo looks pretty good.
https://github.com/shane-mason/cable-box
I'll close this issue in a day or so unless you have more questions.
Superstar thank you! (didn't even realise there was a repo for the box - I am an idiot :-)
Awesome - as the ways to connect to FS42 grow, I am trying to keep a little separation between the core and the ways to connect to the core. If we're all good here, I'll close this issue and you can make a new one if you hit a snag.
Closing this issue since its been documented.