Hi all - especially Slavec and Tim :-)
I don't know if somebody is on the devuan mailinglist, so I'll place this link here:
https://lists.dyne.org/lurker/message/20171214.132959.b8c0d989.en.html
Could TDE provide official packages or a an official repository for devuan ascii, as KatolaZ ( KatolaZ <katolaz(a)freaknet.org> ) is asking for (see posting below)?
As fas as I can tell, Slavecs repository has been stable for ages now, and it works perfectly with ascii. So ... take the chance?
Nik
Am Donnerstag, 14. Dezember 2017 schrieb KatolaZ:
> On Thu, Dec 14, 2017 at 03:17:22PM +0100, Dr. Nikolaus Klepp wrote:
>
> [cut]
>
> > >
> > > During the sprint, you might also be asked to try/test/check theming
> > > material, new packages, provisional installation material, and the
> > > like. Thanks in advance for any help you will be able to provide.
> > >
> > > Come on: let's put ASCII out.
> > >
> > > The Dev1Devs
> > >
> >
> > @ KDE: KDE3 continued as TDE aka trinitydesktop.orghttps://trinitydesktop.org/ works perfect on jessie. It would be very nice, if it could be included as an alternative DE for all those who like KDE3 but dislike all newer KDE incarnations and the GTK3-stuff.
> >
>
> Hi,
>
> I agree, but this just depends on the availability of the TDE team to
> package it for Devuan. I don't think we have the workforce to do that,
> atm.
>
> Hope this makes sense.
>
> KatolaZ
>
--
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
On Friday 29 December 2017, Kai Peter wrote:
> On 2017-12-28 15:50, Slávek Banko wrote:
> > Hi Kai,
> >
> > the same problem I have seen once reported - I suspect on Slackware.
> > But I
> > do not know how he solved it.
> >
> > The findAttr function is defined in htmlattrs.c, which is directly
> > included into htmlhashes.cpp => so there is no reason to be findAttr
> > considered as an external reference.
> >
> > The only thing that comes to my mind is that findAttr is defined as
> > inline
> > and the compiler does not perform the inlining of this function for
> > some
> > reason.
> >
> > Cheers
> I did comment out the inline definitions and it did compile/link well.
> Lets see if there are side effects later on.
>
> Thanks
> Kai
>
Kai,
I've been building TDE on Gentoo for some time. In comparing our respective compiler options used to build tdelibs, I notice that I had compiled with "-fvisibility=hidden -fvisibility-inlines-hidden". I think this *might* have something to do with your error. Since I had not actually added these options to CXXFLAGS, I believe that they are inserted by cmake when you pass it "-DWITH_GCC_VISIBILITY=ON".
Vince
Hi,
I want to build trinity core and did follow the order at the website. As
it was mentioned as optional I didn't build avahi-tqt and tqca. I have
disabled cups too. Now I get a linker error with tdelibs:
[ 90%] Linking CXX shared library libtdehtml.so
cd /mnt/NAS/Projects/trinity/core/09-tdelibs/build/tdehtml &&
/usr/bin/cmake -E cmake_link_script
CMakeFiles/tdehtml-shared.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE
-DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT
-D_REENTRANT -include tqt.h -I/usr/local/tde/include
-I/usr/local/tde/include/tqt -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE
-DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT
-D_REENTRANT -include tqt.h -Woverloaded-virtual -Wl,--no-undefined
-shared -Wl,-soname,libtdehtml.so.14 -o libtdehtml.so.14.0.0
CMakeFiles/tdehtml-shared.dir/tdehtmlview.cpp.o
CMakeFiles/tdehtml-shared.dir/tdehtml_part.cpp.o
CMakeFiles/tdehtml-shared.dir/tdehtml_run.cpp.o
CMakeFiles/tdehtml-shared.dir/tdehtml_factory.cpp.o
CMakeFiles/tdehtml-shared.dir/tdehtml_settings.cc.o
CMakeFiles/tdehtml-shared.dir/tdehtml_events.cpp.o
CMakeFiles/tdehtml-shared.dir/tdehtml_ext.cpp.o
CMakeFiles/tdehtml-shared.dir/tdehtml_pagecache.cpp.o
CMakeFiles/tdehtml-shared.dir/tdehtml_iface.cc.o
CMakeFiles/tdehtml-shared.dir/tdehtml_printsettings.cpp.o
CMakeFiles/tdehtml-shared.dir/tdehtmlimage.cpp.o
CMakeFiles/tdehtml-shared.dir/kjserrordlg.cpp.o
CMakeFiles/tdehtml-shared.dir/htmlpageinfo.cpp.o
CMakeFiles/tdehtml-shared.dir/tdehtml_iface_skel.cpp.o
-L/usr/local/tde/lib
-Wl,-rpath,/usr/local/tde/lib:/mnt/NAS/Projects/trinity/core/09-tdelibs/build/tdeutils:/mnt/NAS/Projects/trinity/core/09-tdelibs/build/tdeprint:/mnt/NAS/Projects/trinity/core/09-tdelibs/build/kjs:/mnt/NAS/Projects/trinity/core/09-tdelibs/build/tdeparts:/mnt/NAS/Projects/trinity/core/09-tdelibs/build/tdeio:/mnt/NAS/Projects/trinity/core/09-tdelibs/build/tdeui:/mnt/NAS/Projects/trinity/core/09-tdelibs/build/tdesu:/mnt/NAS/Projects/trinity/core/09-tdelibs/build/tdewallet/client:/mnt/NAS/Projects/trinity/core/09-tdelibs/build/tdecore:/mnt/NAS/Projects/trinity/core/09-tdelibs/build/dcop:/mnt/NAS/Projects/trinity/core/09-tdelibs/build/tdefx:
java/libkjava.a ecma/libkjs_html.a dom/libtdehtmldom.a
css/libtdehtmlcss.a html/libtdehtmlhtml.a xml/libtdehtmlxml.a
rendering/libtdehtmlrender.a misc/libtdehtmlmisc.a
../tdeutils/libtdeutils.so.1.2.0 ../tdeprint/libtdeprint.so.14.0.0
../kjs/libkjs.so.1.2.0 -ljpeg ../tdeparts/libtdeparts.so.2.1.0
../tdeio/libtdeio.so.14.0.0 ../tdeui/libtdeui.so.14.0.0 -lfreetype
-lfontconfig -lXext ../tdesu/libtdesu.so.14.0.0
../tdewallet/client/libtdewalletclient.so.1.0.1 -lacl -lattr
../tdecore/libtdecore.so.14.0.0 ../dcop/libDCOP.so.14.0.0
../tdefx/libtdefx.so.14.0.0 -ltqt -lqt-mt -lXrender -lX11 -lc -lz
-lXcomposite -lICE -lSM -lutil -lpcre
misc/libtdehtmlmisc.a(htmlhashes.cpp.o): In function
`tdehtml::getAttrID(char const*, int)':
htmlhashes.cpp:(.text+0x27b): undefined reference to `findAttr(char
const*, unsigned int)'
collect2: error: ld returned 1 exit status
make[2]: *** [tdehtml/CMakeFiles/tdehtml-shared.dir/build.make:521:
tdehtml/libtdehtml.so.14.0.0] Error 1
make[2]: Leaving directory
'/mnt/NAS/Projects/trinity/core/09-tdelibs/build'
make[1]: *** [CMakeFiles/Makefile2:9838:
tdehtml/CMakeFiles/tdehtml-shared.dir/all] Error 2
make[1]: Leaving directory
'/mnt/NAS/Projects/trinity/core/09-tdelibs/build'
make: *** [Makefile:130: all] Error 2
It seems that there is something missing - but what? What have to be
linked? Do I have to install some additional package/lib? I couldn't
locate `findAttr(char const*, unsigned int)' yet. Any help is
appreciated. My OS is an up-to-date Gentoo.
Thanks
Kai
--
Sent with eQmail-1.10
Hello,
could someone please add
Devuan Jessie
and
Devuan ASCII
to the OS list of Bugzilla's reporting interface at bugs.trinitydesktop.org?
Thanks,
msi
On Sunday 10 December 2017, Jim wrote:
> On Sat, Dec 9, 2017 at 19:21 (-0800), Vincent Reher wrote:
>
> > Hello TDE Developers,
>
> I am not a TDE developer, but if you are willing to hear from random
> people on this olist...
>
> > I recently purchased a Dell XPS15 laptop for my daughter and before
> > I turn it over to her, I am experimenting to see what must be done
> > to make it usable under Linux/TDE for those with no better than
> > normal eyesight. Per EDID, the laptop's native screen resolution is
> > 3840 x 2160 and its physical screen dimensions are 346 x 194mm
> > (~15.6" diagonal). My objective is to run the laptop at native
> > resolution both inside and outside of X (no re-scaling).
> I am using a macbook pro (2880x1800 on a 15" screen) and a 4K 27"
> monitor, and I went through this a while back.
>
> Having said that, while I use various TDE programs, I don't use TDE's
> window manager, so this advice may not work for you.
>
> <snip>
>
> > Of course, if HiDPI issues have already been addressed by others in
> > the post R14.0.4 source code, that would be great.
>
> I solved a lot of problems by putting
>
> export GDK_SCALE=2
>
> in my ~/.xprofile, which gets read by /etc/X11/xdm/Xsession,
> /etc/tde/tdm/Xsession and /etc/kde/kdm/Xsession (at least on my
> system) and helps a lot of GTK3 programs look reasonable.
>
> It shouldn't hurt (too much) to give this a try. I'd be interested in
> knowing how it works out.
>
> It is too bad that so many software designers assume that screen
> resolutions would be 90 - 100 DPI for all time.
>
> Cheers.
>
> Jim
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
> For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
> Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
> Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
>
>
Hi Jim,
I think the Firefox I am using was built to utilize GTK+-3.x. If that is correct, I did not see any issues with it despite the fact that the GDK_SCALE environment variable is not set.
I am curious about one thing you mentioned: are actually using TDE (the desktop environment per se) with a window manager other than twin? If so, I would be interested to know how that worked out for you as I had noted that alternative window managers can be configured. That might solve at least the "microscopic window resizing arrows" part of the problem.
Thanks,
Vince
-------------------------------------------------------
On Monday 11 December 2017, Dr. Nikolaus Klepp wrote:
> Am Montag, 11. Dezember 2017 schrieb Vincent Reher:
> > On Sunday 10 December 2017, Jim wrote:
> > > On Sat, Dec 9, 2017 at 19:21 (-0800), Vincent Reher wrote:
> > >
> > > > Hello TDE Developers,
> > >
> > > I am not a TDE developer, but if you are willing to hear from random
> > > people on this olist...
> > >
> > > > I recently purchased a Dell XPS15 laptop for my daughter and before
> > > > I turn it over to her, I am experimenting to see what must be done
> > > > to make it usable under Linux/TDE for those with no better than
> > > > normal eyesight. Per EDID, the laptop's native screen resolution is
> > > > 3840 x 2160 and its physical screen dimensions are 346 x 194mm
> > > > (~15.6" diagonal). My objective is to run the laptop at native
> > > > resolution both inside and outside of X (no re-scaling).
> > > I am using a macbook pro (2880x1800 on a 15" screen) and a 4K 27"
> > > monitor, and I went through this a while back.
> > >
> > > Having said that, while I use various TDE programs, I don't use TDE's
> > > window manager, so this advice may not work for you.
> > >
> > > <snip>
> > >
> > > > Of course, if HiDPI issues have already been addressed by others in
> > > > the post R14.0.4 source code, that would be great.
> > >
> > > I solved a lot of problems by putting
> > >
> > > export GDK_SCALE=2
> > >
> > > in my ~/.xprofile, which gets read by /etc/X11/xdm/Xsession,
> > > /etc/tde/tdm/Xsession and /etc/kde/kdm/Xsession (at least on my
> > > system) and helps a lot of GTK3 programs look reasonable.
> > >
> > > It shouldn't hurt (too much) to give this a try. I'd be interested in
> > > knowing how it works out.
> > >
> > > It is too bad that so many software designers assume that screen
> > > resolutions would be 90 - 100 DPI for all time.
> > >
> > > Cheers.
> > >
> > > Jim
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
> > > For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
> > > Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
> > > Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
> > >
> > >
> >
> > Hi Jim,
> >
> > I think the Firefox I am using was built to utilize GTK+-3.x. If that is correct, I did not see any issues with it despite the fact that the GDK_SCALE environment variable is not set.
> >
> > I am curious about one thing you mentioned: are actually using TDE (the desktop environment per se) with a window manager other than twin? If so, I would be interested to know how that worked out for you as I had noted that alternative window managers can be configured. That might solve at least the "microscopic window resizing arrows" part of the problem.
>
> If you are adressing a GTK appication here, then the "microscopic window resizing arrows" is comming from some genuis in GNOME. You can search the mailing list for my adventures. Anyway, this might help (or not any more, as GNOME "matures"):
>
>
> # der GNOME W$&"§%$§:
> # GTK3: ~/.config/gtk-3.0/settings.ini
> $ dconf write /org/gnome/desktop/interface/cursor-size 32
>
> # GTK2: ~/.gtkrc-2.0
> $ lxappereance
>
> # ~/.gtkrc-2.0
> gtk-cursor-theme-size=48
>
>
>
> >
> > Thanks,
> > Vince
> >
> >
> >
> > -------------------------------------------------------
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
> > For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
> > Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
> > Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
> >
> >
>
>
>
Although my primary concern is getting QT3/TDE right, your response reminds me to continue paying attention to GTK*, which I had to work with in the past to ensure that fonts are sized and displayed correctly in applications using those toolkits. I must admit that I never cease to be amazed by decisions to use binary file formats (e.g. dconf) to store simple configuration data.
I can see that you are a big fan of GNOME :)
On Monday 11 December 2017, E. Liddell wrote:
> On Sat, 9 Dec 2017 19:21:19 -0800
> Vincent Reher <tde(a)4reher.org> wrote:
>
> > The remaining issue concerns TDE window/menu controls that are too small. These include window resizing double-arrows, window scrollbar and associated up and down arrows, the menu-submenu right arrow, list expand-collapse (+/-) controls, checkboxes, and radio buttons.
> >
> > I suspect that these resources are part of QT3 but don't really know for sure. I suspect QT3 because applications that do not use that toolkit (e.g. LibreOffice and Firefox) do not manifest the problem.
> >
> > I am hoping that somebody more knowledgeable about GUI configuration and programming can point me in the right direction. Is this something that can be corrected via a configuration file (e.g. qtrc)? If not, can somebody point me to where in in the source code tree I should be looking and what I would need to do to correct this?
>
> Widget appearances are dictated by the style code, which is applied by QT3. You would
> have to either fix QT3 or create a new widget style to make everything correctly HiDPI-sensitive.
> However, you *may* be able to improve your experience somewhat by selecting the "High
> Contrast" style and turning on "Use wider lines" in its configuration. This will make most widgets
> somewhat larger. It isn't the most elegant style, though.
>
> If you are interested in authoring your own widget style (requires C++ knowledge,
> unfortunately), you can find existing styles in tdelibs/tdestyles and tdeartwork/styles.
>
> If you want to patch QT3 directly, my guess is that you would have to look at
> qt3/src/styles/qcommonstyle.cpp , which has a lot of size-related magic constants
> you could play with.
>
> E. Liddell
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
> For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
> Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
> Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
>
>
Thanks, your message was very helpful in clarifying a path forward. I tried the High Contrast style and while I agree that its appearance leaves a lot to be desired, it did seem to remedy matters by presenting larger more visible window/menu controls. That says to me that modifying an existing style might provide a solution to the problem at hand. Perhaps that won't be as modern a solution as a true "it just works" dynamic scaling of these graphical controls, but it will be good enough for me if it allows me to run TDE on laptops such as these at native resolution.
Interestingly, one of the things that was not corrected by that style was the really tiny window resizing cursor. I investigated further and noticed that my favorite cursor theme "Xfree theme redglass" now has an annotation "incomplete for TDE" -- I had never noticed that before. I guess the theme is incomplete because it lacks the "redglass" window resizing cursor. Without it, this particular cursor becomes "Adwaita", a theme that apparently doesn't scale at all. I guess I will also have to learn how to "complete" the redglass theme.
-------------------------------------------------------
Hello TDE Developers,
I recently purchased a Dell XPS15 laptop for my daughter and before I turn it over to her, I am experimenting to see what must be done to make it usable under Linux/TDE for those with no better than normal eyesight. Per EDID, the laptop's native screen resolution is 3840 x 2160 and its physical screen dimensions are 346 x 194mm (~15.6" diagonal). My objective is to run the laptop at native resolution both inside and outside of X (no re-scaling).
Using the EDID metrics, it is pretty easy to determine during boot an optimum terminal font (ter-i32b.psf) and X font scaling (Xft.dpi=240). After that, using the TDE control panel to increase panel and icon sizes produces a nice looking desktop environment … almost.
The remaining issue concerns TDE window/menu controls that are too small. These include window resizing double-arrows, window scrollbar and associated up and down arrows, the menu-submenu right arrow, list expand-collapse (+/-) controls, checkboxes, and radio buttons.
I suspect that these resources are part of QT3 but don't really know for sure. I suspect QT3 because applications that do not use that toolkit (e.g. LibreOffice and Firefox) do not manifest the problem.
I am hoping that somebody more knowledgeable about GUI configuration and programming can point me in the right direction. Is this something that can be corrected via a configuration file (e.g. qtrc)? If not, can somebody point me to where in in the source code tree I should be looking and what I would need to do to correct this?
Of course, if HiDPI issues have already been addressed by others in the post R14.0.4 source code, that would be great.
Thanks in advance for your insights and help.
Vince Reher
Being a bit busy at the mo (and maybe a little lazy) can anybody tell me
if there are significant differences between TDE for Debian & Devuan? If
I were using Debian Stretch _without_ systemd, which would be the better
choice of TDE install?
Cheers,
Mike.
--
Mike Howard
On Saturday 09 December 2017, Felix Miata wrote:
> [I am not a developer.]
>
> Vincent Reher composed on 2017-12-09 19:21 (UTC-0800):
>
> > I recently purchased a Dell XPS15 laptop for my daughter and before I turn it
> > over to her, I am experimenting to see what must be done to make it usable
> > under Linux/TDE for those with no better than normal eyesight. Per EDID, the
> > laptop's native screen resolution is 3840 x 2160 and its physical screen
> > dimensions are 346 x 194mm (~15.6" diagonal). My objective is to run the
> > laptop at native resolution both inside and outside of X (no re-scaling).
>
> > Using the EDID metrics, it is pretty easy to determine during boot an optimum
> > terminal font (ter-i32b.psf) and X font scaling (Xft.dpi=240). After that,
> > using the TDE control panel to increase panel and icon sizes produces a nice
> > looking desktop environment … almost.
>
> 15.6" nominal is physically 282.42 DPI @3840x2160 resolution:
> http://fm.no-ip.com/PC/displays.html
>
> 3840x2160 is considered "quad density", aka 4K resolution.
>
> For a little perspective, consider what increased density means drawing icons or
> text characters compared to lower resolutions.
>
> 15.6" nominal is 141.21 DPI @1920x1080 resolution (the HDTV standard).
> The reference DPI, on which web standards are based, and from which most
> software developers worked until production display densities started to
> considerably exceed the standard reference, is 96. A screen that actually is 96
> DPI @1920x1080 would be almost 23".
>
> At the reference, a 16px by 16px icon is comprised at most of 16^2 or 256
> pixels, and measures 4.417mm square. Going down to a 15.6" screen at that same
> resolution shrinks those same pixels into a 141 DPI 3.003mm square space.
> Raising the resolution to *nominal* quad (3840x2160) squeezes those 256px into
> 242 DPI 1.502mm square space.
>
> The converse is that in order to get an icon that was 4.417mm square on a true
> 96 DPI screen to stay that size on a 15.6" screen @1920x1080 would require
> utilizing approximately 554 pixels. On a quad screen, 3840x2160, that jumps to 2216.
>
> Computers can be programmed to scale up objects so as to improve their physical
> size, but with images that comprise the standard 96 DPI icons, their appearance
> cannot be improved to take advantage of higher available pixel density. Higher
> density screens need to have different, and much larger, icons.
>
> > The remaining issue concerns TDE window/menu controls that are too small.
> > These include window resizing double-arrows, window scrollbar and associated
> > up and down arrows, the menu-submenu right arrow, list expand-collapse (+/-)
> > controls, checkboxes, and radio buttons.
>
> > I suspect that these resources are part of QT3 but don't really know for
> > sure. I suspect QT3 because applications that do not use that toolkit (e.g.
> > LibreOffice and Firefox) do not manifest the problem.
>
> TDE and its own applications are QT3-based. QT3's initial release was 16 years
> ago and for all practical purposes its development ended 3.5 years later, mid-2005.
>
> QT3's design foundation is close to two decades old, well before developers had
> to consider escalation of display densities. Some elements could be scaled with
> density, by using units that scaled (e.g. pt, mm or in), but images weren't
> among them. Some design elements used a mixture of pixel units and scalable
> units, while others used one or the other. Compromises were inevitable where
> densities varied more than a little from the standard.
>
> Image scaling simply can't work as well as today's "HiDPI" screens require.
> Either images in additional sizes need to be provided, or a different kind of
> image designed to be scaled need to be provided, or both. QT3 wasn't designed
> for scalable images, and no one ever provided much in the way of additional
> images, or just as, or more, importantly, an effective framework for utilizing
> them without compromises.
>
> Getting TDE off QT3 onto a foundation that fully supports "HiDPI", assuming any
> such open source foundation actually exists at this point, in my estimation
> would require resources several orders of magnitude larger than those available
> to the TDE project.
>
> > I am hoping that somebody more knowledgeable about GUI configuration and
> > programming can point me in the right direction. Is this something that can
> > be corrected via a configuration file (e.g. qtrc)? If not, can somebody
> > point me to where in in the source code tree I should be looking and what I
> > would need to do to correct this?
>
> IMO you're probably facing a choice between using TDE and not using native
> resolution. At a normal viewing distance, 141 DPI ought to be as high a display
> density as anyone with no better than average visual acuity can fully
> appreciate, absent side-by-side comparisons, where differences may or may not be
> detectable without getting closer or using a magnifying glass.
>
> I suggest giving 1920x1080 (physically 141 DPI) a try. The kernel cmdline can be
> configured through the bootloader menu to have it override EDID and use
> 1920x1080. Xorg and thus TDE should use that mode automatically, but if it does
> not, Xorg can readily be configured to use it directly. TDE settings can do same
> if need be.
>
> Fonts in apps generally work best if DPI is a multiple of 24 (96 * 1.25,
> 96*1.50, 96*1.75, etc.), less well at 12X, even less well at 4X or 8X, so at
> 1920x1080 you might wish to try forcing DPI to 143 or 144. 144 is a breakpoint
> in some software design, so you might notice some big differences between 143
> and 144. Depending on how good your daughter's vision is, leaving logical DPI
> set to its 96 default may well prove acceptable with 1920x1080.
>
> > Of course, if HiDPI issues have already been addressed by others in the post
> > R14.0.4 source code, that would be great.
> Leaving QT3 has been suggested, but I've seen nothing on this mailing list or on
> IRC to suggest anyone thinks it could ever happen.
>
> HTH
Felix, thank you for your lengthy if somewhat pessimistic reply.
To be clear, I have no issue whatsoever with the fonts -- they look great on this display with Xft.dpi=240, perhaps in part due to my past efforts at making fonts look reasonable on Linux desktops. And the desktop/panel icons are fine after stepping up to larger sizes (no scaling).
It's just those apparently fixed-size bitmap images used for window/menu controls that are way too tiny. If indeed the problem lies in QT3 and it cannot be "configured away" either during build time or run time, then I simply ask for somebody more knowledgeable to point me in the right direction so I can start looking and experimenting with the source code.
I am also not suggesting TDE be ported to QT>3. I know that is a non-trivial effort and would not be feasible. Also, I am not even sure that QT fixed this problem until the 5.x versions (http://doc.qt.io/qt-5/highdpi.html).
To downsize from native resolution on this laptop would be to admit defeat and loose a touted feature. It's not going to be a problem for my daughter since most of the software she needs to run is "windows only" and the laptop's pre-installed Windows 10 does not seem to have any problem at all. It may be a problem eventually for me should I choose to get a similar laptop and stick with TDE.
