Hello Jonathan, On Saturday, June 8, 2002 at 5:29:39 PM you wrote (at least in part):
>> It would be interesting what signal/message your keyboard wheel >> sends out ... JA> The keyboard's scroll would also be sending the WM_MOUSEWHEEL JA> iirc, That's quite interesting because this would require a special keyboard driver, recognizing special codes sent by the keyboard-wheel and translating them into Windows 'WM_MOUSEWHEEL' messages as this message type is, IIRC, not known to default keyboard drivers, but to mouse drivers supporting wheel mice. Or in other words: it's a drivers issue ... JA> and *should* behave in exactly the same way. If so: yes ... but: JA> Most applications require the window/panel you want to, to have JA> focus. No. 'WM_WHEELMOUSE' is sent with amount of scrolls (multiplied with 120) and coordinates of mouse pointer. That way panels and components can be scrolled without having the focus. THAT's why I think the keyboard-wheel sends something like 'cursor-Up' and 'Cursor-Down' or 'Page-Up' and 'Page-Down' codes ... because they to only work on _focused_ element, while mouse pointer can be positioned on non-focused elements as well. JA> It's pretty standard behaviour, I guess it was either a miss-coded JA> 'feature' in TB! or the drivers weren't properly understood. I think the latter ... because for correctly understanding the drivers messages for a non-standard feature (keyboard-wheel) the developer will need such a device for itself to do some testings on how the driver behaves :-) How will send the keyboard to Moldavia? *GGG* -- Regards Peter Palmreuther mailto:[EMAIL PROTECTED] (The Bat! v1.60q on Windows 2000 5.0 Build 2195 Service Pack 1) Listen to my music, and hear what it can do ________________________________________________________ Current Ver: 1.60q FAQ : http://faq.thebat.dutaint.com Unsubscribe: mailto:[EMAIL PROTECTED] Archives : http://tbudl.thebat.dutaint.com Moderators : mailto:[EMAIL PROTECTED] TBTech List: mailto:[EMAIL PROTECTED] Bug Reports: https://bt.ritlabs.com
