Awesome! I'll just have to suppress my instinct to type / before my search.
perfect timing, i was just about to submit a better version xD. it is still not perfect because it might miss some modifier keys or some edge cases, but now it will reliably detect and react to standard keypresses and backspace too. all other keys will focus it regardless of interacting with the text box so it should be mostly fineAwesome! I'll just have to suppress my instinct to type / before my search.
Until now I was using Tab which usually focused the search bar. But depending on what was clicked last it could do something different.
That exactly the main reason I made this tool. All the others tried to interact with the games on disk and manage them. This in turn made them complex to setup and have way too many options. I will not turn F95Checker into that, it will not interact with games on disk
Good catch. Before it used the image URL to determine what extension to use to save, but GAB found a bug where if the url doesn’t have the image extension, like many image hosting websites do, it would try to put /‘s and \’s in the name, ending in a file not found error. So the fix was load the image in memory and figure out what format it is. But PIL isn’t able to read that format apparently. So the fix because another bug
It should have already been??? I’ll look into it, guess I messed something up while implementing BG mode...
WillyJL
# run in same terminal where you're starting F95Checker.sh
# or put to ~/.XXXprofile to apply it on every boot, e.g. to ~/.zprofile
# or put to ~/.XXXenvto apply it on every boot, e.g. to ~/.zshenv
export QTWEBENGINE_CHROMIUM_FLAGS="--no-sandbox"
# or run
QTWEBENGINE_CHROMIUM_FLAGS="--no-sandbox" ./F95Checker.shchecked again and it does not render while in the system tray. are you sure you didnt simply minimize it instead of putting it to tray? to put it fully into tray you need to use the BG mode button. either way i pushed a fix and a build and now it also doesnt render when simply minimized to icon.
id love to help but i just cant manage to reproduce these issues... if you have some logs or any other insight that might help
I only can suggest to try latest Manjaro on virtual box
Do you have any suggestion how to turn on max possible level for logging?
Waited few mins for 339 build, nothing happend
While debugging (from start to "login window appeared" after manual refresh)
Yea that’s not so useful. Also it’s intentional that asklogin isn’t reached: both webgine and f95checker use OpenGL to render and I never managed to figure out the contexts, so they didn’t want to run in the same process. I make it run in a separate subprocess (that’s what api.login does, it spawns the subprocess and communicates with it) in the hopes that it doesn’t interfere, and it never has in my experience but that might be the issue? Try to run
./F95Checker asklogin "https://f95zone.to/login"UPD:
QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" ./F95Checker asklogin "https://f95zone.to/login"QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" ./F95Checker, but it didn' work. Probably because login screen opened in new processexport QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu"
./F95CheckerSo my final thoughts - easiest way to "fix" this is just include additional bash script for every release
Yeah, I know. But in my head it's more likeblackop oh my friend env vars can be changed from inside Python! Also I’d imagine there’s a way to pass these options when opening the window itself... either way thanks for you input I’ll fix this directly in Python code
Yes that’s true, but I’ve hardcoded more specific stuff in the past xD. Just consider the binaries: I build them on GitHub actions which run Ubuntu, and their version is in libffi 7 while arch is on libffi 8 and so it refused to run. So I just made it include the server’s libffi 7 in the build. Same on macOS, it expects libintl which I think comes from homebrew and I hardcoded it in... also I feel like disabling gpu and disabling sandbox might be helpful on other OSs too, they’re not really needed for such a simple task like logging in and they might just get in the way like they did hereYeah, I know. But in my head it's more like
Oh my bad, just checked again and seems that the case. False alarm, sorry