-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doublecmd fonts become dots Linux QT5 Sway/Wayland. #286
Comments
Hi, I guess it can be some incompatibility with XWayland, see also #193 |
Thx, that could be it, although with current pascal + lazarus version doublecmd seems to run natively on wayland. Damn why did you chose to write it in pascal? that's an odd choice of a programming language. |
Current version use XWayland by default. How to execute on native Wayland written here. Because Pascal is a great and pleasant language. But it undeservedly forgotten today. |
For me it is not odd at all. It is a more than the right choice. Note these features:
And if I look at TIOBE ranking for December 2021, I see that Object Pascal is #16 as the most searched for programming language. So it's not all that forgotten. It's just burried in a lot of modern day crap. @siyia2: How can this be an odd choice? How many languages do you know that can do this? |
Efficiency wise C is the King it seems and it is widely supported. I would argue in saying that C is the mother/father of modern programming languages, and plus the only language i know to use in some detail :) |
bruh |
lol ok |
@siyia2: It is possible that C could be a little more efficient, but if I have to guess, I would say by a small percent only. |
bruh2 |
a Bloated queen at that
I ll take the queen no prob lol |
:))) |
Hello, i figured this was a general issue with qt5 in wayland enviroment.
in /etc/enviroment resolves the font issue |
Hello, sometimes when i change workspace back n forth, or the screenlocker runs, all fonts in doublecmd-qt5 become dots. Happens only with qt5 version of the program.
The text was updated successfully, but these errors were encountered: