This is awesome, I might have to add a wheel mouse to my carputer.
I'm soooooo glad it uses .NET![]()
I like it, really cool.
[H]4 Life
My next generation Front End is right on schedule.
It will be done sometime in the next generation.
I'm a lesbian too.
I am for hire!
This is awesome, I might have to add a wheel mouse to my carputer.
I'm soooooo glad it uses .NET![]()
AMD XP 2600+/512MB RAM/120GB hard drive
Opus 150W/DVD/GPS/7" Lilliput TS/802.11g/Bluetooth
Installed.
-GPSSecure- - GPS Tracking
-AltTabber2.2.2- - Handy touchscreen utility.
Skinning to go... VisualDesigner2!
[H]4 Life
My next generation Front End is right on schedule.
It will be done sometime in the next generation.
I'm a lesbian too.
I am for hire!
As I metioned before, I've updated MouseWheelInput to provide the capability of using other hardware for input than a wheel mouse only. This is how it works:
All you need is the piece of software labled "Driver" to translate the input device commands into MWI commands. These are:
The only message that is transmitting a parameter is WM_WHEELSCROLL, which has to describe the scrolling direction in lParam:Code:WM_WHEELBUTTONDOWN = WM_USER + 0 WM_WHEELBUTTONUP = WM_USER + 1 WM_WHEELSCROLL = WM_USER + 2 WM_ENTER = WM_USER + 3 WM_BACK = WM_USER + 4 WM_SWITCHMODE = WM_USER + 5
>0 - scroll up
<0 - scroll down
Messages have to be sent using
Whereas the handle can be determined usingCode:SendMessage(handle, message, wParam, lParam)
To enable this feature, set <UseMouseHook> to false in the configuration file.Code:handle = FindWindow(null, "MouseWheelInput")
A driver also may communicate via the FrodoComm interface. This can be accomplished by sending a specific notification (with PostMessageById or PostMessageByName) with:
FrodoCommMessageType : SET
FrodoCommMessageEventName: INPUT
FrodoCommMessageFormat: TEXT
The FrodoCommMessage can be one of these:
As you see also in the picture above, keystrokes can be sent to Windows or to FrodoComm (with a PostMessageBroadCast message).Code:WHEELBUTTONDOWN WHEELBUTTONUP WHEELSCROLLUP WHEELSCROLLDOWN ENTER BACK SWITCHMODE
To make it work with FrodoComm instead of Windows, set option <UseFrodoComm> to true in the configuration file.
You'll get then a FrodoCommMessageType Notify with FrodoCommMessageEventName KeyPress and a Xml message like this one:
<Key virtualKey="65">A</Key>
Enjoy playing around![]()
Skinning to go... VisualDesigner2!
Great Concept![]()
Ikea Case. Epia M10000.M1-ATX. 512 Mb. 2,5" 80 GB HDD. 7" Lilliput. BU-303 GPS. Sony Joystick.
Status --> Lilliput Installed (not indash yet..)
BraveCar 2.5
Skinning to go... VisualDesigner2!
Upon a improvident comment of Brave (), I've added a new feature that will collect all input and lookup for matching words in a dictionary.
![]()
If you're using a touch screen, this will improve the input a lot.
Since a dictionary is plain text, you can easily edit and expand it to adapt it to your needs.
To enable this feature, place the filename of the dictionary file within tag <Dictionary>. By default the list shows only 5 entries but you can alter this setting by setting <MaxDictionaryList> to any number.
Skinning to go... VisualDesigner2!
LOL
it rocks![]()
![]()
Ikea Case. Epia M10000.M1-ATX. 512 Mb. 2,5" 80 GB HDD. 7" Lilliput. BU-303 GPS. Sony Joystick.
Status --> Lilliput Installed (not indash yet..)
BraveCar 2.5
MWI now also supports task switching too:
![]()
Let's see, who's the first to figure out how it works![]()
Skinning to go... VisualDesigner2!
Bookmarks