Permanently unbind ctrl-v

[djskankho]

I've been searching the forums trying to find out about unbinding keys. Everytime I restart SageTV ctrl-v is always bound to "TV" even after unbinding. Is there any way to manually and/or permanently unbind this key combo?

[Opus4]

Using Detailed Setup -> Commands -> Unlink _should_ do the job. How are you running SageTV? Are you running the service and have both the service & SageTV start at bootup? If so, try not having the UI portion auto-start & then start it after the PC boots. There may be a problem using the correct properties file when both the service & UI start at bootup.

Try exiting/restarting SageTV and then try unlinking that command again.

- Andy

[djskankho]

Originally Posted by Opus4

Using Detailed Setup -> Commands -> Unlink _should_ do the job. How are you running SageTV? Are you running the service and have both the service & SageTV start at bootup? If so, try not having the UI portion auto-start & then start it after the PC boots. There may be a problem using the correct properties file when both the service & UI start at bootup.

Try exiting/restarting SageTV and then try unlinking that command again.

- Andy

SageTV does not run at startup. I've tried unlinking multiple times in a row, completely restarting sage using it with and without the sagetvservice.

The real problem is that I'm using the MCE remote and apparently the back button registers control-v as well as the back command in sage. So I need to unbind control-v but it just won't go away. Each time I restart it comes back bound to tv. I've been trying to unbind for a few days now; not by hitting the back button on the remote because that just sends me back, just by unlinking control-v.

I've tried looking in the properties files but haven't found anything particularly useful. Could this be an stv problem? I have SageMC up now but used to run MlbDude2 and Cayars.

[Opus4]

Originally Posted by djskankho

The real problem is that I'm using the MCE remote

Yes, that is the real problem in this instance. See this info about the MCE remote button commands. The Back button sends a Windows message, not Ctrl+V. Unless you can change the message that button sends, there is no way to remove the Back functionality, since you can't change the meaning of that message in SageTV.

You may very well have been unlinking the Ctrl+V command (unless it really shows up listed in the Commands -> Link...Command list), but it won't have anything to do with the MCE remote.

- Andy

[djskankho]

I really am unlinking the ctrl-v command and it comes back in the list after I restart sage. The back button works fine after I unlink until I restart.
...
OK, so apparently I'm just an idiot and girder was sending crtl-v to sage...but that still doesn't explain why I can't unbind that command. I guess it's not real urgent now but does anyone have any ideas? Thanks, Opus, for your help.

[Opus4]

I've really got to read more carefully. I confused that last mention of the Back button with Ctrl+V being stuck on the Back command, which is how I used it for a while. Then, I thought the back _message_ was being sent & you didn't want it to mean Back. I don't know if my previous reply made any sense at all now. Let's back up a bit (no pun intended)...

The key bindings _should_ be saved to the properties file at some point, usually when you exit SageTV. Are you rebooting w/o exiting SageTV first? I don't think you should have to do so, but maybe it isn't getting a chance to finish writing the properties file. Have you tried changing the Ctrl+V command link, immediately exit SageTV, then run SageTV.exe? If that _is_ what you've already done (I probably missed that above too ), is the properties file read-only? Is it somehow getting corrupted & replaced with the backup copy instead? Strange!

Also, the UI on the server uses different properties files depending on whether you are using the service (sage.properties) or not (sageclient.properties), so if you switch the service on/off, you may have to relink your commands if the other prop file hadn't been configured the same way.

- Andy