Semen Yesylevskyy

@andwin Btw, one person is now using my fork on github to make an Arch Linux package of qtgrace. I'll let you know whether he encounters any problems.

@andwin concerning the compilation errors. In Fedora 42 GCC 15 is used, which switched to C23 standard by default. Legacy yacc files have to be compiled with C17 standard, otherwise they won't pass the stricter checks of new standard. I implemented this in CMake in my fork but I don't know how to enforce the standard in qmake (should be a matter of setting a compiler flag). There is also a problem in server.h with incorrectly placed include guards leading to multiple definition errors (also fixed...

Dear @andwin thanks a lot for your reply! Maybe you can look at the issue, which I reported in 2023 concerning the absence of any antialiasing in KDE? (https://sourceforge.net/p/qtgrace/discussion/1358965/thread/ecd4b996fe/) This issues still persists now in Fedora 42 KDE and I suspect that it is somehow related to Wayland vs. X11 but I don't have enough knowledge to localize it. Also, I've recently made a fork of QtGrace on github for myself that uses CMake instead of qmake and compiles with Qt6...

Dear @andwin, is QtGrace still alive or you abandoned it?

Thanks for quick reply! I don't see any antialiasing settings in the printing dialog and the general preferences of QtGrace. I have "Qt fonts" and "symbol fonts is special" selected, but I don't see any switch for antialiasing. It is also weird that the preferences dialog is displayed normally, but the color selection pop-up is not antialiased (attached), so I gues that something is definetely wrong. The KDE uses custom color scheme, but the widget style is a standard Breeze, so I wonder what can...

First of all, I'm QtGrace user for many years and I want to thank a lot for this fascinating software! I recently switched from Linux Mint to Fedora 38 KDE and suddenly there is no antialiasing of fonts and lines in QtGrace (see screenshot). I've deleted the .ini file and recompiled QtGrace with no effect. Is this a Fedora-specific bug? It looks strange because this is KDE editiion and all othe Qt apps work flawlessly. Any suggestions are appreciated!