XSCREENSAVER VS XAUTOLOCK PATCH
With this patch the behaviour of FO didn't change, but at least we have the same source base to compare. Since the most of them are W32 stuff, and the non-linux related source files are removed from debian source package, I only had to patch this: So the first thing I made was to patch libois-1.3.0 package with the changes of the FreeOrion version. The debian version is based in the 1.3.0 stable (with some additional fixes), but FO uses the actual HEAD of SourceForge (r40 in or master branch of GitHub. But before that, let me say that the libOIS version packaged in Debian testing and the version in the FreeOrion sources are not exactly the same. I've got a way to go around it, applying one of the pending pull requests from. There are several messages in the libois forums with the same symptoms, for example this: So here it is:ĭefinitely it's a libOIS related issue. I've sent a message with my research to the Debian bug, but I think you may be also interested. Hello, I'm one with this error in his setup (I'm using Xfce). However, it does suggest that to help debug the main problem here we could perhaps compile a special version of FO for this user to test, that adds some keypress logging at essentially the same spot as this patch, to see just what key presses, if any, are getting through to FO in his situation.Īlso potentially of interest - some other folks dealing with this and other problems with standard OIS, looking at using SDL with possibly an OIS wrapper. To reiterate/clarify, the attached patch is a hack-ish potential fix for the alt-tab problem, not for the main problem reported here. Attached is a little patch for that if we want to consider using it.
XSCREENSAVER VS XAUTOLOCK MODS
What I did with our current setup is just have the GiGiOgrePlugin_OIS (via OISInput.cpp) nullify any alt mods before passing on keypress events to GG/Ogre, which seems to work fine since FO currently doesn't use the alt key for anything I know of (though I suppose I'm not entirely sure if some non-english keyboard settings might rely on it for certain characters).
XSCREENSAVER VS XAUTOLOCK WINDOWS
I suppose I could just swap in the linux files from sourceforge though, or just try implementing it all via OISInput.cpp, but it also looks like the ability to force a re-read of key states which the Windows fix relied on is not available for the LinuxKeyboard (though perhaps I could just force a reinitialization of it after an alt-tab).
It seems that our OIS version has had some linux build support files stripped out so I can't even modify it and build it in Linux if I uninstall my standard ois library.
On the alt-tab issue, it appears it's a known problem with OIS, which they seem to have only fixed for windows. I'm not familiar enough with the xtrace log to get anything useful from it at this time, perhaps someone else here can. Hmmm, I see the user replied, and was able to verify the alt-tab problem as a distinct issue from his more significant problem.
0 kommentar(er)
