 | ||||||||||||||||||
|
||||||||||||||||||
 | ||||||||||||||||||
| ||||||||||||||||||
|
||||||||||||||||||
| ||||||||||||||||||
| ||||||||||||||||||
| ||||||||||||||||||
|
||||||||||||||||||
|
|
|
|
|
| ControllerMate Device Scanner | ||||
|
|
|||||
 |
 |
 |
The OrderedBytes Forum -> Controller Types | |||
|
||||||||
|
|
|
|
|
|
|||
|
Ken
Developer  Joined: 27 Mar 2006 Posts: 2122 |
Over the course of the last several months, there have been many offers from users to do some additional testing on devices in order to help make them more compatible with ControllerMate. Until now, there hasn't really been a good way to do this.
CM Device Scanner (download) is a little application that allows users to run four specific tests on their devices. The results from these tests will help create a downloadable Controller Type file for those devices. The four tests are: 1. Unnecessary Controls -- Sometimes (particularly for keyboards or keyboard/mouse combinations) ControllerMate shows hundreds of controls in the Palette window that just don't exist on the device. During this test, the user presses all of the buttons/controls on the device to determine which of the claimed controls are real and which are not. 2. Rename Controls -- Some controls have strange default names. This test allows users to submit more meaningful names for controls. 3. Non-Standard Controls -- By default, ControllerMate ignores controls that don't have standard definitions. This test will collect basic information about controls that are being ignored, and will record the events that these controls generate. This will help make ControllerMate compatible with devices that use non-standard controls. 4. Verify LEDs -- Some devices claim to have an interface to LEDs. This test will attempt to blink each LED in turn and allow the user to indicate whether or not there actually is a blinking LED on the device. These tests will be most useful for keyboards which have a variety of additional media buttons. Typical joysticks/gamepads usually show up correctly in ControllerMate and won't benefit by this. All tests are optional. CM Device Scanner is intended to be a self-explanitory, step-by-step application. As such, there isn't a separate help file or ReadMe. Questions about it should be posted here or sent via e-mail.  _________________ Ken www.orderedbytes.com - www.controllermate.com ControllerMate -- Programming controllers for Mac OS X since ... well ... recently. |
|||||||
|
||||||||
|
||||||||
|
|
|
|
|
|
|||
|
Tursaanpoika
Joined: 16 Jul 2010 Posts: 5 |
Hiya Ken!
I'm trying to map my whole MX3100 desktop but as far as I've read those files CMDS creates, the media keys somehow seem to belong to the mouse 1133:50450:1:2 (keyb is 1133:50450:1:6). I've not yet purchased CM, but it looks promising - if only there was a way for me to make a controller... Is there? I like to tinker around myself, but I cannot grasp "spurious" for example. Logitech's own Mac-support/driver is a plain joke. (MX3100 isn't mac-compatible, I know, but still...) |
|||||||
|
||||||||
|
||||||||
|
|
|
|
|
|
|||
|
Tursaanpoika
Joined: 16 Jul 2010 Posts: 5 |
Actually, I think I got it:) I'll send you the .cmate-file and the CMScanner .plist later on. |
|||||||
|
||||||||
|
|
|||
| Page 1 of 1 | All times are GMT - 6 Hours | |||
|
|
|||||
|
|
|
The OrderedBytes Forum -> Controller Types | |||
|
|
|
| You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum |
||
|
|
|
|
|
|
|
 |
|
|
|
Copyright © 2005 — 2010 OrderedBytes All rights reserved. |
||||