Open Arcitec opened 2 months ago
Thank you for opening this issue. May I mention that this is also an issue for non-system Python installations in general? We install a Python interpreter using uv and have also very ugly rendering. A solution for this is not known to us.
We install a Python interpreter using uv and have also very ugly rendering. A solution for this is not known to us.
Interesting. Didn't know that uv
manages the python interpreter too.
The only solution would be if uv
can install a version of tk
build with libXft support somehow. Maybe their repo needs a report about that.
We install a Python interpreter using uv and have also very ugly rendering. A solution for this is not known to us.
Interesting. Didn't know that
uv
manages the python interpreter too.The only solution would be if
uv
can install a version oftk
build with libXft support somehow. Maybe their repo needs a report about that.
It is quite awesome. I opened an issue. Thanks for your support.
There's around a million different open issues and discussions in your repo, where people are asking why CustomTkInter is pixelated and uses tiny fonts when running inside Conda.
For example, all of these duplicate tickets and many more: #2593 #1757 #1620 #1358 #1400 #1384 #1620 #1271 #931 ... and more!
I've investigated and found the answer: Conda installs
tk
into all environments by default, but uses a version built without support for FreeType/TrueType, font detection, Unicode or antialiasing. This is why the UI looks like total garbage inside Conda.I have posted the solution in a comment on Conda's issue tracker. And you can add the same instructions to your readme/installation wiki (to hopefully reduce the amount of bug reports you're receiving about this):
https://github.com/conda-forge/tk-feedstock/pull/40#issuecomment-2381409555