Page 1 of 1
Problem with font's
Posted: 19 Jun 2017, 14:17
by pd8b
I did tried a lot but can't find any solution.

- Knipsel.PNG (28.97 KiB) Viewed 4253 times
You see that my font on the right is not easy to read for me. I there any solution where you can change it?
tnx!
Pd8B
Re: Problem with font's
Posted: 19 Jun 2017, 22:48
by DF5WW
Have you set your Windows to a higher percentage than 100% ?
Log4OM can only handle 100% so if you set your Windows to a
higher percentage (e.g. 125%) you will have problems like this.

- df5ww1.png (29.73 KiB) Viewed 4247 times
Re: Problem with font's
Posted: 23 Jun 2017, 23:39
by pd8b
DF5WW wrote: 19 Jun 2017, 22:48
Have you set your Windows to a higher percentage than 100% ?
Log4OM can only handle 100% so if you set your Windows to a
higher percentage (e.g. 125%) you will have problems like this.
df5ww1.png
Thank you!
this did fix my problem! Now it is okay.
Thanks for youre tips!
73 PD8B
Re: Problem with font's
Posted: 03 Aug 2017, 16:02
by pd8b
DF5WW wrote: 19 Jun 2017, 22:48
Have you set your Windows to a higher percentage than 100% ?
Log4OM can only handle 100% so if you set your Windows to a
higher percentage (e.g. 125%) you will have problems like this.
df5ww1.png
Thought it was fixed. But it is only a one time solution. When i change it.. it asks me to logout. Then it's okay. But when i shutdown windows.. and restart it is set back to another size so Log40m is again to large font.
Any tips to make it more permanent?
( i changed it under admin account)
Re: Problem with font's
Posted: 04 Aug 2017, 00:08
by DF5WW
Hi OM (a Name in the signature would be useful),
it looks like a Windows related problem. Log4OM is using the Windows size.
Could be possible that you change the size in Windows but it will not be saved.
Try to set the size in Windows to 100 % and with the right Mousekey in the
Desktop screen klick on "Actualize" ... Sorry don“t know the Windows messages
in english, here in DL it means "Aktualisieren" ..
Think that this is not a Log4OM related problem. Here all ist working fine since
generations of new Log4OM versions ...
