|Joystick-To-Mouse: for Windows; Run Windows with a Joystick!; Version 2.80 Release 6; User's Guide|
|Prev||Chapter 6. Advanced User Notes||Next|
Windows 8 Notes
Special use executables: Included in the installation folder are three executables for Joystick-To-Mouse - JOY2MSE.exe, JOY2MSE.highestAvailable.exe, and JOY2MSE.requireAdministrator.exe. Depending on the configuration of User Account Control (UAC) and the specific needs of an individual user, there can be situations where one of the optional executables may be more appropriate. If necessary, rename JOY2MSE.exe to JOY2MSE.asInvoker.exe, then rename the desired optional executable to JOY2MSE.exe. These contain requested execution levels in the manifest for handling by the system. Due to User Interface Privilege Isolation (UIPI) concerns, these will allow operation for different applications and special usage situations. For example, if a application is elevated to Administrator, Joystick-To-Mouse may not operate as desired if running as the default "asInvoker" execution level. By using the "highestAvailable" or "requireAdministrator" executables, Joystick-To-Mouse will be elevated when the process is started.
Version: Windows 3.1
The program simply does not conform to the Windows standards, and Joystick-To-Mouse cannot operate within the painting area. The program does not allow other programs to run while a mouse button is depressed for paint operations. If necessary, use a real paint program.
2.50 Note: While testing to alleviate this problem, it was discovered that once the painting operation was begun (i.e. Mouse button down (to draw)), Paintbrush did not return control to the Windows operating environment. The 3.1 version maintains control and does not allow other applications to operate until the painting operation is complete (Mouse button up)). This is considered bad-behavior within Windows (or any multi-tasking, or pseudo-multi-tasking environment), and Microsoft has updated and fixed this "bug" in their Windows 95 release.
In testing, the Up-button message apparently does not get received by button controls in the Access environment, although Windows control buttons (Minimize, Maximize, Close, etc.) do operate properly. This probably revolves around the timing & "object" events highly integrated within Access - why this should affect an external application, or the up-button message sent from Joystick-To-Mouse may be attributed to the GetAsyncKeyState API, or something else within the Access application.
|Joystick-To-Mouse Developer Utilities||Up||Joystick-To-Mouse Initialization File Description|