-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
Direction controls... #66
Comments
This will be coming in due course. |
Added cursor.py, and updated remote.py to include sendEnterKey. |
@Tenzer this is largely just hooking up cursor.py to the command line interface at this point as far as I can tell. Maybe you're interested? |
@klattimer I had a quick go at this today, I could however not get the websocket connection for |
@Tenzer not yet, I haven't had the time to look at it recently, I wrote the code a while back and had to dig it out from a couple of different places to push it up. I'll dig around on here and see if I can see why it's not triggered. |
This would be an issue here I think.
|
I got it working and I've made a PR with a new command for this in #147. The problem was the command |
I'm not much up on my python/sockets, but I have a node script which I've extended to get cursor controls (left/right/up/down/click etc) working
Would you be able to extend yours to incorporate? They are really useful when using the built-in/downloaded Apps.
I see you already have getCursorSocket but are not yet using it?
In Node, I have a function for each direction/command, which runs:
The scripts connect to the TV, run the direction command (which gets and then opens the pointer socket) and passes a command to it) - and then calls a disconnect on the socket
input_pointer_send is just issuing the commands to the opened socket.
pointer is declared globally as null, and then set once the pointer socket is opened and reset to null on disconnect
The text was updated successfully, but these errors were encountered: