Skip to content

Conversation

@MATRIX-feather
Copy link
Contributor

Fixes #22, may fix #23

Checked how CocoaInput handles X11Controller earlier, and looks like we need to make these callbacks as standalone fields to make sure they work and not crash the game.

IBus seems to work, Fcitx5 requires to enable "On The Spot" however, so this pr also includes a troubleshooting guide for these users.

Copy link
Owner

@LemonCaramel LemonCaramel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your contribution! I was late in reviewing this because I don’t have a device that runs X11 (and I still don’t).

To be honest, I don’t fully understand why changing the callbacks to standalone fields resolves the issue. I suspect it might be a memory allocation problem in JNA caused by garbage collection.

In any case, since I’ve received reports that this PR does resolve the problem, I’ve decided to merge it. Once again, I’m truly sorry for the delay.

@LemonCaramel LemonCaramel merged commit 17a6478 into LemonCaramel:master Apr 10, 2025
1 check passed
LemonCaramel pushed a commit that referenced this pull request Apr 10, 2025
* Make callbacks in X11Controller as standalone fields

* Add troubleshooting guide for Fcitx5

* Let's just reboot the machine
LemonCaramel pushed a commit that referenced this pull request Apr 13, 2025
* Make callbacks in X11Controller as standalone fields

* Add troubleshooting guide for Fcitx5

* Let's just reboot the machine
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

Successfully merging this pull request may close these issues.

2 participants