Logitech/AST Remote plugin

[Ron]

I'm currently swamped in work ( when am I ever not :sad: ) I'll hook up the ast receiver and check this when I get some time, you might want to bump this one in a few days (weeks ?)

[Ron]

Okay,.. i've fixed the AST plugin, there is however 1 catch, the plugin is only compatible with the new Girder 3.1 so if you want this fix, you'll have to upgrade and live life on the edge for a few days :smile:

The plugin is included in the new distro.

<font size=-1>[ This Message was edited by: RonB on 2002-03-06 22:36 ]</font>

[Mark F]

Welcome to Girder!

It looks like the ast.dll file was left out of the version 3.0.23 package. I don't know why. The file is available in the version 3.0.22 .zip file that is on the download page. Un-zip this particular file into the Girder3pluginshardware directory.

To set up this plugin: Start Girder and enable the plugin by choosing the file/settings .../hardware plugins page. Find the NEC/AST/IBM plugin in the list and place a check mark next to it. Choose Apply. High-light the NEC/AST/IBM line again and choose settings. Set the com port and press Apply or OK.

[kg3]

I saw that Girder supports the Logitech/AST remote (said on "features" on web site) but I can't find the plugin for it. Do I have to use a generic plugin? I saw on the developer page that it is plugin 6 but it's not included in the package I downloaded nor can I get it off the web site. Why is this plugin not available?

[jessb45]

Is there any way I could disable the automatic mouse buttons in this DLL but not the movement pad. I like the way that the mouse movement is already set, but the buttons (the 3 blue ones below the movement pad on the ast remote) don't do what I want and the signal never reaches the program.

[jessb45]

The click buttons have a seperate output for both the click and release. When you press one of the click buttons, a signal is transmitted to click the mouse. When you release it, a signal is transmitted that is supposed to release the click. However, nothing happens to that signal. (I beleive that the interpreted code that girder receives is 255 for both the right and left buttons.)

So if you could just get 255 to release the click, it would enable you to use the remote with the same capeabilities as a regular mouse. You could hold the click for as long as you wanted and use the mouse to drag items, etc.

Right now, if you use one of the buttons, the mouse gets out of sequence and behaves strangely.

Please let us know if you have developed a fix, looked into it, or if there is an updated plug-in.


<font size=-1>[ This Message was edited by: jessb45 on 2001-12-30 20:58 ]</font>

[jessb45]

...

<font size=-1>[ This Message was edited by: jessb45 on 2002-01-30 02:35 ]</font>

[Nikolai]

Same problem here, on Windows XP.

[lbushby]

I'm also having problems with the mouse button support on my AST remote. It appears that when I use a blue button on the remote it acts as if the relevant mouse button is held down but not released. Is this a known problem and if so is there a solution?

(I'm running Windows 2000 in case that makes a difference).

--
Luke Bushby

[lbushby]

Will do, thanks for the response.

[FreeJack]

Bump for RonB's reminder. :smile:

[BSUGUY]

I am having the same problem but am getting the 255 code on several of the buttons, number pad and the mouse controls.