2007/10/25

I tried installing AMouse and now I don't have a mouse object anymore

Some of the latest AMouse installation packages (in the 2.7x release numbers) have a problem when registering the class replacement for the mouse object. As a result, after installing AMouse you can find you don't have anymore a mouse object in the "System Setup" folder.
Paul Ratcliffe posted a simple solution to this problem: copy the following lines into a text file with the name mouseobj.cmd (or whatever.cmd), then execute the script from the command line or simply by double-clicking the icon.
/**/
call RxFuncAdd 'SysLoadFuncs', 'REXXUTIL', 'SysLoadFuncs'
call SysLoadFuncs
class = 'WPMouse'
title = 'Mouse'
location = '<WP_CONFIG>'
setup='NOCOPY=YES;NODELETE=YES;NOPRINT=YES;
DEFAULTVIEW=SETTINGS;OBJECTID=<WP_MOUSE>;'
call SysCreateObject class, title, location, setup, 'R'

Please note that the "setup=..." line, which is wrapped here due to space limits, must be joined back to form a single line of text.

Many thanks to Dario Ragazzini for the suggestion!

2 comments:

Unknown said...

Hi Cris,

Copying and pasting didn't work here on eCSV2.0RC1 as the "wp_config" needs to be "WP_CONFIG", as in Paul's original. Although all standard WPS ID seem to be uppercased, the "wp_mouse" will create the Mouse object.
On posting this the following was displayed:
Your HTML cannot be accepted: Tag is not allowed: - referring to the angle-brackets where the double-quotes are in the above!

Mike O'Connor

Cris70 said...

Thank you very much for your comment Mike!
I'll correct the sample ASAP.

Cris