On 8/5/2023 6:01 AM, Paul wrote:

So something is wrong with the graphics.

The title and decoration for the window, is a different call and
subsystem than the "pixmap" that makes the window contents. Perhaps
it has a minimum version of OpenGL ?

Bingo!

Thanks to Paul and Vanguard for all the help. This page gives what
finally accomplished getting this program working again. I clicked to
use "OpenGL Software" and it restarted and now works!

<https://help.tomtom.com/hc/en-us/articles/360013960139-MyDrive-Connect-not-displaying-or-starting-correctly-after-update>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 8/5/2023 11:03 AM, sticks wrote:

On 8/5/2023 6:01 AM, Paul wrote:

So something is wrong with the graphics.

The title and decoration for the window, is a different call and
subsystem than the "pixmap" that makes the window contents. Perhaps
it has a minimum version of OpenGL ?

Bingo!

Thanks to Paul and Vanguard for all the help.  This page gives what finally accomplished getting this program working again.  I clicked to use "OpenGL Software" and it restarted and now works!

<https://help.tomtom.com/hc/en-us/articles/360013960139-MyDrive-Connect-not-displaying-or-starting-correctly-after-update>

I could see the signature for "ANGLE" support in the collection
of executables. But it was unclear to me, why it would ever bother
to use ANGLE.

ANGLE is some sort of Google-developed scheme, to support
an OpenGL-like API, on top of DirectX somehow. It might have
been suited to an older piece of equipment or an older OS.
As pure OpenGL didn't always aspire to the "latest version"
and some of the OpenGL would not be suited to running whizzy
modern applications (there were games in the past that would not
run, because "my OpenGL was too old").

libGLESv2.dll \___ What the application thinks it is calling
libEGL.dll /
D3Dcompiler_47.dll --- How the calls are supported on hardware

opengl32sw.dll --- Historically, we're used to "opengl32" without
the "sw" on the end. That's been available for
over 20 years (opengl32.dll) in crusty old
graphic card packages, and you copied that into
your game folder. This, presumably, is yet another
custom glue layer of some sort. Filenames should be
8 characters, rather than the 10 characters of
this splotch.

It's pretty hard to understand what their graphics logic is in Qt5,
whether they have a preference or a flow-chart for selecting a method.
You can be assured though, that they would never call DirectX3D directly, because that would be admitting to a "non-FOSS" approach to building
a framework.

Something about your drivers, must have made it do this! (Mis-behave).
That's why that log file might indicate something is up.

I would have preferred though, that TomTom keep a startup log,
with info on any "missing" driver content, recorded in plain language.

I used Stellarium (a planetarium application), as a similar Qt5 application, just to see what little hints it might deliver. I used "procmon" from Sysinternals, to catch it writing to a logfile, which is how I located
the location of their particular progress logfile. But I guess the two applications
do not share exact details as much as I'd hoped.

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 8/5/2023 10:59 AM, Paul wrote:

On 8/5/2023 11:03 AM, sticks wrote:

On 8/5/2023 6:01 AM, Paul wrote:

So something is wrong with the graphics.

The title and decoration for the window, is a different call and
subsystem than the "pixmap" that makes the window contents. Perhaps
it has a minimum version of OpenGL ?

Bingo!

Thanks to Paul and Vanguard for all the help.  This page gives what finally accomplished getting this program working again.  I clicked to use "OpenGL Software" and it restarted and now works!

<https://help.tomtom.com/hc/en-us/articles/360013960139-MyDrive-Connect-not-displaying-or-starting-correctly-after-update>

I could see the signature for "ANGLE" support in the collection
of executables. But it was unclear to me, why it would ever bother
to use ANGLE.

when I tried it today, it was not quite all there visibly, so I went
back to that settings page from the hidden tasks and clicked on it to
use OpenGL angle. It then restarted and works just fine again. Weird
as hell.

ANGLE is some sort of Google-developed scheme, to support
an OpenGL-like API, on top of DirectX somehow. It might have
been suited to an older piece of equipment or an older OS.
As pure OpenGL didn't always aspire to the "latest version"
and some of the OpenGL would not be suited to running whizzy
modern applications (there were games in the past that would not
run, because "my OpenGL was too old").

libGLESv2.dll \___ What the application thinks it is calling libEGL.dll /
D3Dcompiler_47.dll --- How the calls are supported on hardware

opengl32sw.dll --- Historically, we're used to "opengl32" without
the "sw" on the end. That's been available for
over 20 years (opengl32.dll) in crusty old
graphic card packages, and you copied that into
your game folder. This, presumably, is yet another
custom glue layer of some sort. Filenames should be
8 characters, rather than the 10 characters of
this splotch.

It's pretty hard to understand what their graphics logic is in Qt5,
whether they have a preference or a flow-chart for selecting a method.
You can be assured though, that they would never call DirectX3D directly, because that would be admitting to a "non-FOSS" approach to building
a framework.

Something about your drivers, must have made it do this! (Mis-behave).
That's why that log file might indicate something is up.

I would have preferred though, that TomTom keep a startup log,
with info on any "missing" driver content, recorded in plain language.

That same settings page has a checkbox to enable detailed log files.
After checking it it produced four files. dx.diag.log, Launcher.log,
Log.txt, and qtdiag.log.

There does seem to be a lot of information in there contacting their
support staff could have used.
In the end, it seems to me this is a problem from the TomTom software
people in figuring out how to use available Win 10 resources to make
their app work. It's not really a Win 10 problem, just making it run in
the operating system. I realize you can't test every hardware setup,
and that in the end the solution was right in front of me. I'm not the savviest of users, but far from a novice. Argghh! At least it works
now, or should I say, "For now."

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)