The last page of the updater has a very very little font size. This is not a functional problem - I can click finish and it went away but it isn't looking nice.
Screenshot here:
Screenshot: capture_001_2023-04-19_22-58-07.png
New: Run-Command (Dec 2, 2024), Platform 29.5.3 (Jun 27, 2024)
1,100+ portable packages, 1.1 billion downloads
No Ads November!, Please donate today
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
What operating system are you using (version, build, 32 vs 64-bit), what resolution (1920x1080, etc), and what scaling do you have set (200%, 300%, etc)?
Sometimes, the impossible can become possible, if you're awesome!
machine: AMD Ryzen 7 2700X, Eight-Core Processor, 3.70 GHz
RAM: 16.0 GB
version: Windows 10 Pro
build: 19044.2856
32 vs 64-bit: 64 bit
resolution: 2560x1440
scaling: 100%
It works without issue here. Did you remove any Windows system fonts like Segoe UI or Tahoma? Could you check your registry to see if you have a key of HKLM\Software\Wine? What this looks like is that the platform is attempting to set a font that doesn't exist. And then it's defaulting to something else, what looks like a pixel font of some sort on your machine.
Sometimes, the impossible can become possible, if you're awesome!
Look by yourself, please:
Since adding Linux/macOS Wine support, the PA.c Platform figures out the font name and size and passes that to the PA.c Updater/App Store via an environment variable. It looks like that might not be making it through. Is there anything on your system that might interfere with environment variables? Can you try rebooting and see if that alleviates the issue?
Sometimes, the impossible can become possible, if you're awesome!
OS : Windows 11 22H2 64 bits
Resolution : 1920x1080
scaling : 125%
I haven’t seen anything in my environment variables that could interfere
It wouldn't be any set environment variables that would interfere, it's more if something is interfering with the ability for a process to pass temporary environment variables to another it launches, as is happening here. After a reboot and doing the same thing does it work?
Sometimes, the impossible can become possible, if you're awesome!
After a reboot, same thing
Do you have the Wine registry mentioned above? Are your standard Windows fonts all installed including the updated Windows 11 Segue UI?
Sometimes, the impossible can become possible, if you're awesome!
The "Wine" registry key is not present.
All Windows standard fonts are correctly installed.
Ok, thanks for checking. I have an idea that should work as a fallback in this situation. I should have time to implement it when I get back home.
Sometimes, the impossible can become possible, if you're awesome!
This should be fixed in 26.0 with a workaround to detect issues in environment variable passing and default to Tahoma 8 which should be on every Windows system.
Sometimes, the impossible can become possible, if you're awesome!
Yes, it's fixed !
Thank you very much
Nice - and well done!
Thank you, John.
Nice work!