mousewheel and jit.window
I have a large standalone in which I would like to be able to use the mousewheel to be able to rapidly scroll through values in a number box.
I know that jit.window has a mousewheel parameter, but I’m clueless as to how to use it within a patch that otherwise doesn’t use any Jitter at all, let alone a jit.window?
Also, how does one interpret the data that comes out of jit.window for the mousewheel parameter? I can’t make heads or tails of it…
I’ve had a look at this one year ago to help someone on the forum but couldn’t find any way that doesn’t involve a jit.window. The mousewheel speed is given with something like this (but I guess you had figured this out…). I got values ranging from about -0.5 to 0.5 :
<code>-- Pasted Max Patch, click to expand. --Copy all of the following text. Then, in Max, select New From Clipboard.----------begin_max5_patcher---------- 565.3oc0U1sipBCDG+Z3ongq8XZKBBm61miMmroHiZMPqoTTO6l8c+zVDkc8 KjrZxIpzzoiS+O+Xl1O78Bxj6fp.zuQuh779v2yyYxZva+bufR1tYErJmaAy jkkfPGLpYMMrS6rWJqqfsKAn.sgUTCsNrlomsjKV7lBloa1HJd5X7HTLNwNP hv1Ap4I5O6+SyUKxr9ZWowBO2sKxrU+hhai8boPKXkfaoWTbVQ2Up3u6VgPO DEQcIWT.ZWpPNZTVqashsF+z229XTOYx7BoIHWIiIQjwQGx3yjvcRORxsSu0 LkwtFTuABVVgyi1brIWz+cMzr2V0wLuuPAYLwhfiLdvHhN.DIfslj6jpl2KF KzKQD7sgWzzTG7huJ7huM7NAPV1bebg9n4hFkgJtVKTLtoRx0IERs.5RLIc. HwUpb2X4gWtnLgEPGOp41DZxTGgH3zqU1P+OqpoDppXKfS3CMLEQL+vc+L17 kFhmjD1ilrHpiS6oV5E5xvCgWmmUg2CqH+bkRq35wa4hb4VzFdNHuFalF4Jk lLooTxMPIWfM+7cagCsayEtfBt36Ww6RRq8uxsJYsZVqn1mLHxAQkCUZtfo4 RQGeL8NnijXIOOGDcuOJmWYuhJ+xWt1W070c57pI8oolzdvFaiRGmdzxA2G4 7bny21pKnm3mmdh6idRFndZZzXqWuATU6ioSJlihVIU1owibS4hlotl2.Erg 25+DmElxb5i1bzSsp4jicIwA9184S++Apwqql. -----------end_max5_patcher-----------
Can’t you use the hi object to get the mousewheel info? I don’t have a mouse to test, but i see that if i scroll on my trackpad (mbp) i get numbers such as 6 1, 6 2, 6 3 or 6 -1, 6 -2, 6 -3… If i don’t use the scrolling function i always get 6 0..
edit: actually it works with an usb mouse and hi on my mbp: param 10 not 0 if scrolling (1 or -1 for each step)…
@Tobias – the hi object is a good idea, I will give it a look.
@Stephane – thanks, I had also gotten that far, but I think there is more to interpreting the info than just looking at that last value… Either way though, I can’t have a jit.window be the frontmost window in my application, so I don’t think it would work for me anyway…
Follow up on using the hi object – it does work, but the bad news is that on two different mice I’ve looked at on two different systems, the code that the hi object outputted for mousewheel movement differed. So coming up with something that will work across systems (which for me is a requirement) doesn’t look promising.
Forums > Jitter