Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for controller hotplugging #44

Open
MurrayMcDonald16 opened this issue Jun 19, 2018 · 0 comments
Open

Support for controller hotplugging #44

MurrayMcDonald16 opened this issue Jun 19, 2018 · 0 comments

Comments

@MurrayMcDonald16
Copy link

A number of forums suggest periodically using reflection to get the DefaultControllerEnviorment and instantiating a new instance in order to detect a "new" or replugged controller. This technique works, however, it causes a memory leak of DIDeviceObject and DIComponentObject instances as well as HashMap entries where the DiDeviceObject is used as a key.

g3force added a commit to g3force/jinput that referenced this issue Jul 3, 2018
g3force added a commit to g3force/jinput that referenced this issue Jul 3, 2018
g3force added a commit to g3force/jinput that referenced this issue Jul 3, 2018
g3force added a commit to g3force/jinput that referenced this issue Jul 3, 2018
g3force added a commit to g3force/jinput that referenced this issue Jul 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant