This works (almost) perfectly. A great tool, something whithout which I'd kill my mouse.
Unfortunately, I had to upgrade my development environment from Visual Studio 2008 to Visual Studio 2010. In '2008, XMBC's mouse wheel scrolling worked in nearly every window, but in '2010 it does not work at all, that is, I have to click in every window, every dialogue and on every bloody control for it to get the scroll wheel messages.
Attempts to use the "Advanced Window Scrolling" functionality fail, since both the Window Class name and Parent Class name seem to contain characters which confuse XMBC.
Opening the "find window" editor, I choose a text editor window in VS2010 and get for instance "HwndWrapper[DefaultDomain;;a2f30edb-7850-4f40-a487-958dbb9e770e]" (as class name) and "HwndWrapper[DefaultDomain;;7af17adc-e1b4-42e6-8835-cccb1ab57190]" (as parent class name), but upon re-opening the "find window editor", the class name gets shortened to "HwndWrapper[DefaultDomain" and the parent class name gets scrambled to "a2f30edb-7850-4f40-a487-958dbb9e770e]", which is the rest of the original class name and not the parent class name at all.
A peek in the XML configuration file shows this as
Code: Select all
<Application Name="W:devenv.exe;HwndWrapper[DefaultDomain;;00c003d5-6d4e-4423-aeb0-1cea8d1842a6];HwndWrapper[DefaultDomain;;7af17adc-e1b4-42e6-8835-cccb1ab57190]" Description="" Enabled="true" InvertScrolling="false" ScrollPages="false" AxisLocking="true" ScrollLines="3" AdvScrollMethod="8" AdvScrollVert="1" AdvScrollHorz="1">
Anyway, even if this worked, it wouldn't be a solution, since every edit window inside VS2010 has a different window class name.
Do you see any chance for a remedy? Any chance to get the scroll wheel back to it's functionality?
Thanks for any enlightening thoughts
Postscriptum:
I forgot to mention the environment:
Windows 7 SP1 x64 Enterprise
Visual Studio 2010
Logitech RX250 optical wheel mouse, using Windows' own HID Mouse driver for it.