Support for variable DPI settings in user session (range 64-512) has been added to TDE and will be part of the upcoming R14.0.11 release. This should help using TDE with high resolution screens. Go to TCC -> Appearance & Themes -> Fonts page and there is now a spinbox control to set the font DPI in the mentioned range. See screenshot here showing KCalc at 3 different DPI settings. https://mirror.git.trinitydesktop.org/gitea/attachments/6413bbc0-dee7-453e-… Updated packages in PSB/PTB will available soon. For the other distros, you will need to wait for the R14.0.11 release I guess. Cheers Michele

On 07.10.21 03:57, Michele Calgaro via tde-devels wrote: Hello, wow thank you very much! It works very well. I still adjusted the icons. I also tried the last week scaling with xrandr. This is not good, much too blurry. I have tried Q4OS in a VM for the last few days. There is a scaling program for TDE. There are the icons, font and so with one setting changed. But I don't want to use Q4os, because TDE has been changed a bit. I do not like it. The scaling tool has the advantage that I can simply change it all when I pull the monitor from the laptop and again have a smaller resolution. It is very comfortable. Best regards

Stefan Krusche composed on 2021-09-29 10:10 (UTC+0200): Xft.dpi is the means by which TDE-Control -> Appearance -> Fonts: "Force DPI for fonts:" is applied. When this is used, it is stored in ~/.trinity/share/config/kcmfonts as forceFontDPI= under [General]. With TDE closed, you can put any number you please here and it will stick. Not app apps are affected by Xft.dpi. Xft.dpi is the "knob" by which Gnome/GTK font scaling is applied. If you wish non-adherent apps to use your specific DPI, X itself needs a DPI forced. Various methods can do this: 1-DisplaySize in /etc/X11/xorg.con* can do it. 2-The xsession startup script can do it with a -dpi switch. 3-Xrandr can do it with -dpi option either via startup script, which will affect the entire session, or after startup, by which it will only affect apps started after running it. This latter method can be helpful in choosing an optimal value. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

Slávek Banko composed on 2021-09-30 10:07 (UTC+0200): Providing only 96, 120 and none is arbitrarily limiting. If it was up to me, there would be a checkbox to enable forcing, and an input box instead of a select list, which would reject irrational entries, such as those <36 or >360, and be prefilled with either 96, or if greater than 96, a value calculated from any image size reported in Xorg.0.log. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

Hi all, On Thu, Sep 30, 2021 at 11:52 (+0200), Slávek Banko wrote: Keep in mind that not all monitors correctly report their dimensions, and even for those that do, sometimes you have to bend backwards to get the info. For example, while get-edid works fine (for me) on some monitors, no others it returns incorrect information, and on yet others it returns no info at all (in my case, this happens on some external monitors; YMMV). In the end, I use the following function and command-line below (the function was glommed from some place on the internet and modified somewhat, I regret I've lost the original author, so I can't give proper credit. my_get_edid_as_ascii_hex () { while read -r output hex conn do echo "$hex" done < <(xrandr --prop | awk ' !/^[ \t]/ { if (output && hex) print output, hex, conn output=$1 hex="" } /ConnectorType:/ {conn=$2} /[:.]/ && h { h=0 } h {sub(/[ \t]+/, ""); hex = hex $0} /EDID.*:/ {h=1} END {if (output && hex) print output, hex, conn} ' ) } The following command line spits out all the information, you could add ' | grep DisplaySize ' to output just the line which has the size. my_get_edid_as_ascii_hex | xxd -p -r | parse-edid Having said that, some monitors report the wrong size with that function, and for my own purposes I use the following function get_screen_name () { while read -r output hex conn do # original: # [[ -z "$conn" ]] && conn=${output%%-*} # echo "# $output $conn $(xxd -r -p <<< "$hex")" printf "%s %s\n" $output $(xxd -r -p <<< "$hex") done < <(xrandr --prop | awk ' !/^[ \t]/ { if (output && hex) print output, hex, conn output=$1 hex="" } /ConnectorType:/ {conn=$2} /[:.]/ && h { sub(/.*000000fc00/, "", hex) hex = substr(hex, 0echo a, 26) "0a" sub(/0a.*/, "", hex) h=0 } h {sub(/[ \t]+/, ""); hex = hex $0} /EDID.*:/ {h=1} END {if (output && hex) print output, hex, conn} ' | grep $1 ) } which was modified from the one found at https://stackoverflow.com/questions/10500521/linux-retrieve-monitor-names Finally, I have a function which uses the screen name returned by get_screen_name() to see if it is a monitor I know (which otherwise reports the wrong size) and pick the correct size, and otherwise the function crosses its fingers and uses the reported size and number of pixels to calculate the DPI. This works fine for me because I can update the function with monitors that I use which give the wrong info, but it is not a very general solution for the world at large. This whole thing is a vessel of fertilizer and it stinks. You'd think it would be easier in 2021. Cheers. Jim

Michele Calgaro composed on 2021-10-01 10:31 (UTC+0900): -100 Without a text input option, sliders are terrible A11Y/U9Y. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

On 2021-10-02 02:50:48 Dr. Nikolaus Klepp wrote: But having better control over the DPI setting would be a start; these other issues might best be submitted as a separate bug report. Leslie -- Operating System: Linux Distribution: openSUSE Leap 15.3 x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.0.10 tde-config: 1.0