New ebuild for games-puzzle/blocks-that-matters (BTM for short) Reproducible: Always Tested with the package comes with humblebundle "Humble Voxatron Debut" When the game start despite in full screen keyboard doesn't work because WM doesn't focus on it, you have to Alt-Tab it to focus and get the keyboard and sound works right. Can't figure out how to solve it so far.
Created attachment 291609 [details] Main ebuild
Ame, thanks for the ebuild. I'm attaching an update for 1.0.0.8 that includes a few changes/updates. The biggest difference is that there's (now?) a native 64-bit version available, so I made a few edits support both the amd64 and x86 packages. There are a couple other minor cleanups in there as well. One change that I'm not sure about and wanted to specifically call out was changing the java dependency from sun-jre-bin to virtual/jre. I figure depending on the virtual package is better in case someone prefers openjdk or whatever. I know some programs will only work with the Sun/Oracle binaries, but in this case I couldn't find any documentation that specifically says it's required, so I switched it to the virtual. If anyone knows otherwise, please let me know and I'll flip it back.
Created attachment 293977 [details] games-puzzle/blocks-that-matter-1.0.0.8.ebuild
(In reply to comment #0) > When the game start despite in full screen keyboard doesn't work because WM > doesn't focus on it, you have to Alt-Tab it to focus and get the keyboard and > sound works right. > > Can't figure out how to solve it so far. I get a different behavior with 1.0.0.8. It starts in full-screen and gets proper focus (after delay in starting up), but the resolution is wrong. It's too narrow and tall for my monitor, so the top and bottom is cut off. And, weirdly, I have a full-screen monitor, so I'd expect the sides to be cut off if anything. All of the full-screen options have issues, but switch it to windowed mode seems to work fine here, in very limited testing.
Great work Jared B. I did'nt even notice a new version came out. Honestly i didn't do so much testing on java version and stuff (and I don't know how the virtual/ stuff works XD ) so I think the virtual is a good way for what you said "in case someone prefers openjdk or whatever" Tomorrow I'll test the new version and take a look at the screen resolution issue...
