>>9431
>>9430
Thank you for these updates. Let me know if you discover that hydrus is related to the BSODs.
You can force a 'last session' save under
help->debug->gui actions->save last session.
>>9433
>>9435
Thanks for letting me know–I am glad it turned out ok. I will write in a little hook that notices if the program fails to boot with an older exe than the db and report it to the user.
>>9438
Christ, what a mess. The Linux Pyinstaller 'wrapper' that makes the build work does some weird environment stuff. I wonder if that is doing this. It looks like the cwd is somehow the hydrus dir or something there, so mpv is pulling the .so files from hydrus?
Some additional error information is supposed to pop up if you try to open externally if you have
help->debug->report modes->callto report mode turned on. If you do that, do you get a 'attempted to launch…' popup (you'll get some other spam as well) with a sensible output, or is something getting borked?
>>9439
I am not sure, I haven't thought about this. This is this stuff–
test
–right? I wonder if there is some way of me matching those characters to ascii live, so even though you are typing regular, it'll still get those results. There's some crazy unicode ① ② ③ stuff like this as well, where it counts as a digit but not a decimal or something if I test it. I will look into this.
I don't remember the exact specifics, but I
usually discount syntax/weird characters when you type. Maybe I am just doing some regular ascii stuff. I'll see if stuff like that dot are getting excluded as well.
>>9440
>>9441
>>9446
The ride never ends, lads. I completely fucked myself with dupes, and in the past couple of years, the rise of CloudFlare type services is now serving dupe after dupe, often completely on-the-fly without the original site realising.
I don't know the endpoint here, but my rough suspicion is that detecting exact dupes, where it is just a resize or resave-at-lower-jpeg-quality, is actually an easy problem to solve. So maybe in a future iteration of the duplicate system, I can write in some automatic steps here, so if it downloads an image it
knows it already has a higher quality version of, it can just merge and discard the shit one automatically. Machine Learning may also help for the more difficult tasks, and I'm slightly hoping that in ten or fifteen years ML just replaces all artists and generates perfect art on demand, thus rendering hydrus as an archive program completely pointless and I can just ctrl+a->delete and finally die.
Twitter has a similar problem, where people will post otherwise-good shit that has already been reposted back and forth between Facebook's and Twitter's CDNs five times, leaving it a jpeg-artifacty mess. I think it is going to get worse before it gets better, and no amount of 'this is where to use jpgs, this is where to use pngs' graphics are going to teach the normies how to do it better.
>>9443
Hey, I am sympathetic to your problem, but I think I read that we aren't supposed to use wxversion any more with wxPython? 4 is installable to virtual environments (i.e. with
virtualenv), so you are really supposed to create a virtual environment with the wx you need and then activate that venv in your run script? Afaik, wxversion doesn't even come with wxPython any more, and it isn't available on pip. I don't have a huge amount of experience with this, but I moved my Linux build environment over to a venv one not long ago and have had great success with it.
wxPython 4 is available on pip, but I have had trouble building it on Linux. However there is a wheel you can get straight from their site that works for me. I have some more info here, if you haven't seen it yet:
https://hydrusnetwork.github.io/hydrus/help/running_from_source.html
I don't know. Let me know if doing it with virtualenv is better for you. If not, I'll see if I can figure out some polite catch with wxversion if installed.