You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Arch Linux, having just installed unknown-horizons-git.
When I left or right scroll using the touchpad (xinput test # button presses 6 or 7),
if I am in the main menu or the New-Game Single Player screen, nothing happens
as soon as a game loads, L/R scrolling immediately exits the program with error
Traceback (most recent call last):
RuntimeError: Caught a director exception
Unknown Horizons exited uncleanly via SIGINT
AL lib: (EE) alc_cleanup: 1 device not closed
If I disable touchpad L/R scrolling, via xinput set-button-map ## 1 2 3 4 5 0 0
where ## corresponds to the touchpad, the crash does not occur.
The text was updated successfully, but these errors were encountered:
frsfnrrg
changed the title
Crash when scrolling left or right in main game mode
Crash when touchpad-scrolling left or right in main game mode
Nov 10, 2017
frsfnrrg
changed the title
Crash when touchpad-scrolling left or right in main game mode
Left/right scrolling with touchpad in main game mode crashes UH
Nov 10, 2017
This looks like the same problem as #2828 and fifengine/fifengine#1062, where horizontal scrolling would also crash the game
This would mean that it is fixed in #2829.
Short summary: UH was implementing a FIFE mouseeventlistener interface, but did not implement the methods for horizontal scrolling. Adding implementations for those fixed it.
On Arch Linux, having just installed
unknown-horizons-git
.When I left or right scroll using the touchpad (
xinput test #
button presses 6 or 7),if I am in the main menu or the New-Game Single Player screen, nothing happens
as soon as a game loads, L/R scrolling immediately exits the program with error
If I disable touchpad L/R scrolling, via
xinput set-button-map ## 1 2 3 4 5 0 0
where
##
corresponds to the touchpad, the crash does not occur.The text was updated successfully, but these errors were encountered: