blight input config file corruption

[GoogleCodeExporter]

From Tillin9 on emutalk:

As far as keyboard and mouse. There is an enable mouse button in Blight. It
doesn't seem to work for me though, i.e. it does grab all mouse events from
the window system, but doesn't move anything in the emulator. Maybe this
might be a bug worth fixing?

Reference: http://www.emutalk.net/showthread.php?p=400999#post400999

Original issue reported on code.google.com by ebenbl...@gmail.com on 8 Apr 2008 at 4:43

[GoogleCodeExporter]

This should be verified/fixed before 1.4.

Original comment by ebenbl...@gmail.com on 22 Apr 2008 at 9:30

• Added labels: Milestone-1.4

[GoogleCodeExporter]

Hmm... some more info. on this one. Blight now seems to get mouse input but 
switching between 1.3 and the latest svn seems to corrupt the Blight config 
file by 
putting -1s in file. My issue was due to the enable mouse being set for 
multiple 
controllers. 

Some simple sanity check logic should fix this.

Original comment by sknau...@wesleyan.edu on 23 Apr 2008 at 11:10

[GoogleCodeExporter]

Yes, I noticed my blight input conf file also got corrupted with -1's at one 
point.
There haven't really been a lot of major changes to blight input since v1.3 (I 
got
sidetracked working on the cheat system), so I'm wondering if this bug existed 
before
then. I'll mess around with it to see if I can recreate the corruption when I 
have time.

Original comment by ebenbl...@gmail.com on 23 Apr 2008 at 11:16

• Changed title: blight input config file corruption

[GoogleCodeExporter]

I do not think this is valid, I'm pretty sure around the time this was posted I 
had
changed the way blight input worked. I do not think this is important for 1.4, 
and
unless you will be actively following up on it ebenblues, I'm taking this off 
the
todo list for 1.4

Original comment by sgorman07@gmail.com on 18 May 2008 at 5:05

• Removed labels: Milestone-1.4

[GoogleCodeExporter]

This is really old, I know at least one blight input config corruption problem 
has
been addressed in the trunk of SVN.  Does anyone still experience this problem?

Original comment by richard...@gmail.com on 3 Jan 2009 at 2:22

• Changed state: Invalid

[GoogleCodeExporter]

This is really old, I know at least one blight input config corruption problem 
has
been addressed in the trunk of SVN.  Does anyone still experience this problem?

Original comment by richard...@gmail.com on 3 Jan 2009 at 2:22