Can mouse scroll wheel be disabled when watching Live TV?

[gordyp]

Several times now while watching Live TV and the Sage TV client has focus, I have used the mouse scroll wheel, thinking I am scrolling a web page, etc. (not noticing that the Sage client window still has focus), and the channel changes - and I end up losing any time-shift I might be using. It is driving me nuts - is there any way to disable the ability of the mouse wheel to change channels in Live TV?

Thanks!

[ryanagler]

bump

[CMO]

bump

[John@TunerUK]

I'd like to know if this is possible too. I sometimes pause live tv whilst I'm on the phone, then come back to tv 30 min's or so later. One accidental scroll of the mouse wheel and the last 30 minutes of paused tv is lost!

[RickE]

This is the single most annoying mis-feature of SageTV that I've encountered.

Does anyone have a solution (or pointer to a solution)?

Thanks and regards,
Rick

PS:

I think I'll file a bug report to be sure that Sage is aware that at least some of us are troubled by this behavior.

[Micco]

+1

Count me in on the "most annoying mis-feature of Sage!".

It looks like all of us who are posting this are all lower-post-count types. So either there is a way that non-new users know about or everyone has just sucked it up and adapted

[TallMomof2]

Send in your suggestion as a bug report, that's the best way to get the programmer's attention. I don't like the active mouse wheel either.

[RickE]

I filed a bug report last night, but haven't gotten a response yet. I'll post whatever I hear from Sage Support.

regards,
Rick

[RickE]

I got the following response from Sage Support. I actually found the indicated lines in my SageClient.properties files (I run in server mode), but changing the numbers to zero fixed the problem.

Close SageTV and the service and open up your Sage.properties file in the
SageTV folder with notepad and look for these two lines:

wheel_down_event_code=12
wheel_up_event_code=11

Change the event codes to 0 or you can try any number above 200. Basically
you should avoid any number between 2-104.

This will disable the wheel.

regards and Happy Holidays to all!
Rick

[hockeyfan]

OMG! It's funny how it's so basic. I was expected some cryptic method to making it not use the scroll wheel.

It reminds me when ppl were talking about using the Hauppauge remote w/the extender and someone asked "how do you get it to work?" someone else replied "you point it at the extender and press the buttons on the remote."

Sage continues to find ways to make me feel humbled at the easy solution.

Thanks for finding the answer to this and Merry Christmas.

[ryanroat]

Originally Posted by RickE

I actually found the indicated lines in my SageClient.properties files (I run in server mode), but changing the numbers to zero fixed the problem.

This is an important note. I found the lines in the sage.prop file, changed them and no change in the scroll wheel effect. Then I saw the above info and found the lines in the sageclient.prop as well, and that was the change that disabled the scroll wheel.

Thanks for the info.

[KryptoNyte]

How do you make the scroll wheel control the volume?

[jamestr234]

i use autohotkey to disable the wheel in Live TV mode AND
enable the wheel in program guide .





wheeldown::
PixelGetColor, pcolor, 832, 42
;;MsgBox The color at the current cursor position is %pcolor%

if pcolor = 0x381d02
{
Send, {pgdn}
sleep 100
}
return

[gordyp]

Originally Posted by jamestr234

i use autohotkey to disable the wheel in Live TV mode AND
enable the wheel in program guide .





wheeldown::
PixelGetColor, pcolor, 832, 42
;;MsgBox The color at the current cursor position is %pcolor%

if pcolor = 0x381d02
{
Send, {pgdn}
sleep 100
}
return

Um - what is Autohotkey? And where do you put the wheeldown code? Could you elaborate a bit on how to accomplish this? This is exactly what I was hoping for - a way to turn off changing the channels but still be able to use the wheel in the Program Guide...

[thatdude90210]

Originally Posted by KryptoNyte

How do you make the scroll wheel control the volume?

Use 13 for volume up and 14 for down.

The list of events you can control is here:
http://www.sagetv.com/2_papers/SageT...wsMessages.txt

And for people who don't use Autohotkey but still want to do something similar, just use 4 and 5 for wheel up and down. The channel won't change with the wheel, and the guide will move up and down, just slower.

[jamestr234]

Originally Posted by gordyp

Um - what is Autohotkey? And where do you put the wheeldown code? Could you elaborate a bit on how to accomplish this? This is exactly what I was hoping for - a way to turn off changing the channels but still be able to use the wheel in the Program Guide...

paste the script into a text file named wheelfix.AHK

install autohotkey

run wheelfix.ahk

i check the color at the top of the sagetv screen to determine
if the active screen is livetv or a menu screen.

if its a menu screen i link the wheel to pagedown/up.

[Sl33man]

Thank you very much,

I was scratching my head for some time wondering what was causing the random channel changes.

Cheers,

Wade

[SoCoolCurt]

i see this thread is pretty old but this issue is driving me nuts. i've made the changes to the properties file but it still continues to change anyway. there has to be another property file somewhere else or something because i've restarted the PC multiple times and can see that the changes are still in the properties file but the channel change still continues. any suggestions?

[SoCoolCurt]

Originally Posted by SoCoolCurt

i see this thread is pretty old but this issue is driving me nuts. i've made the changes to the properties file but it still continues to change anyway. there has to be another property file somewhere else or something because i've restarted the PC multiple times and can see that the changes are still in the properties file but the channel change still continues. any suggestions?

ok nevermind. i got it working. just like i thought, there were more than one property file on my PC. once i changed them it worked perfectly. i think this also incidentally explains some other issues i've been having as well.