PeterBBBBB
PeterBBBBB
It seems the builds intentionally use a different hardware node for each test build. For the build logs currently showing, results are unstable 41 virt64a-armhf-rb cbxi4pro0-armhf-rb 4-1 bookworm 29 cbxi4pro0-armhf-rb...
SDL2/SDL_image.h is usually in the package libsdl2-image-dev Its listed as a build dependency in README.md
I tried implementing the "something like this" exactly as ``` if (apply_xform(cp, fn, p, q, rc)>0) { consec =0; badvals ++; p[0] = q[0]; p[1] = q[1]; p[2] = q[2];...
Its been renamed to https://flam3.com/flame_draves.pdf
I found I needed to use `-std=c++14` to compile testoperators.cpp
There is a command line tool, xbrzscale, that is easier to build and use than Waifu2x. Does scaling up to x6 in one pass, similar quality to Waifu2x
Not a recent regression, same issue with 0.6. Can't build 0.5 with current Qt6 libraries.
Problem seems intermittent. If [OK] is pressed after the font change, it is usually saved. However, if [Apply] is pressed first, it is usually lost.
I guess you meant **un**able to reproduce... ;-) I'm using Xfce with Xorg. I've noticed that font settings are saved after hitting [Apply], but the changes are then overwritten on...
I'm still seeing the problem with latest git. Around 3 seconds after hitting [Apply], the font settings in the dialog are reverted (and that is what is saved on exit)