#22 Alternate input engine

closed-fixed
nobody
None
5
2010-11-15
2010-03-12
Anonymous
No

I wrote a new "Hardware Input Engine" allowing to connect a "Saitek Kasparov PC Auto chessboard" to SCID.

In theory all we should do to enable it in SCID, is select "Tool" / "Connect Hardware" / "Configure", then:
- select "Input Engine"
- change "Engine Command" to the new driver executable (port does not matter with my program as it is hardcoded to /dev/port for parallel port access)
- Press "OK"
Then go to "Tool" / "Connect Hardware" / "Connect Input Engine".

In SCID 4.2.2 this configuration setting is ignored and SCID still tries to call the default "dgtdrv2.i686" executable.

(note there is a temporary workaround: create a link (I use Linux) named "dgtdrv2.i686" somewhere in the "PATH" pointing to other executable.

Nicolas

Discussion

  • Steven

    Steven - 2010-06-24

    After this line, in scid (or scid.gui, or inputengine.tcl)
    set ::inputengine::port $::ExtHardware::port
    Adding this line might fix it
    set ::inputengine::engine $::ExtHardware::engine

     
  • Alexander Wagner

    • status: open --> closed-fixed
     
  • Alexander Wagner

    Solved in current cvs. Thank you for reporting! But please note that the trackers are hardly used in this project please subscribe to the mailinglist.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks