search

Djomanix / bwapi

Automatically exported from code.google.com/p/bwapi
0 stars 0 forks source link

Some keyboard keys crash BWAPI #193

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Some keys on the keyboard when pressed cause BWAPI to crash. Ones I've 
noticed are media controls like play, pause, volume etc.

Original issue reported on code.google.com by quaver.smith on 30 Jan 2010 at 8:31

GoogleCodeExporter commented 9 years ago 
What version? Release or SVN? Revision?

Original comment by AHeinerm on 30 Jan 2010 at 9:43

GoogleCodeExporter commented 9 years ago

Original comment by AHeinerm on 30 Jan 2010 at 9:44

GoogleCodeExporter commented 9 years ago 
Beta 2.6.1

If I debug it, the call stack is at BWAPI.dll!onDrawHigh() line 495 + 0x19 
bytes and 
the output is Unhandled exception at 0x1004762d (BWAPI.dll) in StarCraft.exe: 
0xC0000005: Access violation reading location 0x00000000.

Original comment by quaver.smith on 31 Jan 2010 at 1:45

GoogleCodeExporter commented 9 years ago 
Well my media control keys don't cause any problems.
The only reason it can crash in onDrawHigh is if one of the drawing functions 
were
used incorrectly. There's no possible way keyboard input is related to drawing.

Try the latest revision, if that doesn't work, then you'll have to wait until we
scrap the current drawing hooks in favour of cleaner and portable code.

Original comment by AHeinerm on 31 Jan 2010 at 4:30

GoogleCodeExporter commented 9 years ago 
In some computers, when media controls are pressed, there will be corresponding 
on 
screen display showing the status. It is quite possible that these display is 
incompatible with BWAPI drawing function.

Just a guess ^_^

Original comment by hero...@gmail.com on 31 Jan 2010 at 6:23

GoogleCodeExporter commented 9 years ago 
That would be a huge fault of whatever computer software is being used to 
display it
on screen. It wouldn't be the fault of BWAPI or Starcraft if that was the case,
voiding the issue. I'm still interested to see if the latest revision has any
alternative results.

Original comment by AHeinerm on 31 Jan 2010 at 12:49

GoogleCodeExporter commented 9 years ago 
probably related to issue 195. I'm thinking of just removing the code for the
keystate stuff since it's causing so much problems

Original comment by lowerlo...@gmail.com on 11 Feb 2010 at 11:16

GoogleCodeExporter commented 9 years ago 
The keystate code has already been modified.

Original comment by AHeinerm on 12 Feb 2010 at 2:32

GoogleCodeExporter commented 9 years ago 
Please verify if it still crashes in the latest revision.

Original comment by AHeinerm on 21 Feb 2010 at 9:06

GoogleCodeExporter commented 9 years ago 
closed for inactivity

Original comment by AHeinerm on 28 Feb 2010 at 4:55