Dinesh966 / jnativehook

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

Stops catching events when multiple open #43

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
Can't seem to reproduce when trying to but continues to happen when I am 
testing a program

But my process for testing this program right now is

1. change some code
2. export as executable jar
3. run to test
4. after maybe 20 - 30 minutes keys stop being caught

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
1.1.4
Windows 7

Please provide any additional information below.

Saw the issue before for another version and used the temporary solution of 
logging off/restarting computer

When this occurs I have run the JNativehook jar as well and instead of showing 
all actions no actions come up

http://imgur.com/fhgPwSF

If anything else would help ask I will try to provide the information

Original issue reported on code.google.com by Killma...@gmail.com on 28 Apr 2013 at 2:30

GoogleCodeExporter commented 9 years ago
Your recent nightly works perfectly for me now. 
What's the best way to remove the debug output?

Original comment by blakenoo...@gmail.com on 27 Aug 2014 at 10:56

GoogleCodeExporter commented 9 years ago
Awesome!  Hopefully this change will finally close this bug.  

You can remove most of it by disabling the logger on "org.jnativehook".  There 
is some documentation in the wiki that covers how to change it.

https://github.com/kwhat/jnativehook/wiki/Examples#logging-and-console-output
https://github.com/kwhat/jnativehook/blob/master/src/java/org/jnativehook/exampl
e/NativeHookDemo.java#L178

Original comment by a...@1stleg.com on 28 Aug 2014 at 3:00

GoogleCodeExporter commented 9 years ago
RC1 is now available and it should address just about anything that could have 
caused this bug so I am going to call this one solved at this time.  Please 
test with the latest revision and reopen if it occurs again.

Original comment by a...@1stleg.com on 16 Sep 2014 at 12:07