AnalogClock | This is a live analog clock using HTML CSS | Date Time Utils library

As per my comment on the question, the Qt Kit auto-detected set up for MSVC2019 seems to use the wrong compiler. Though it's certainly possible to use a LLVM (clang) compiler on Windows, I've personally only done this with "official" LLVM distributions (not whatever is included with MSVC).

Anyway, one way to resolve this would be to add the correct Kit manually. The simplest way should be (as per screenshots in the question) to:

1. In the Kit setup, select the existing Desktop Qt6.1.2 MSVC2019 64bit Kit.
2. Use the Clone button to create a copy of it, then select the copy from the list.
3. In the copy, just change the two Compiler options to use Microsoft Visual C++ Compiler 16.10.31424.327 (amd64) (it's OK that they both say "C++" in the name even though one of them is for the "C" compiler).
4. Adjust the kit names so you know which is which in the project settings. Maybe change the broken auto-detected Kit name to include "LLVM" or "broken" or some such to distinguish it. "OK" out of the options dialog.
5. Now in the Project Build Settings you will be able to select the newly added Kit. Just click on it to enable it. You may also want to disable the broken kit (r-click on the kit name for a menu).

Keep in mind that Qt 6.1 is not feature complete yet (not everything from 5.x has been ported), though the included examples should work. Upcoming 6.2 release should be more complete, but still breaks lots of 5.x stuff. To try a more mature version with greater backwards compatibility with most existing Qt projects, use 5.12.x or 5.15.x versions.

The AnalogClock by default takes all the available space of the parents and since widget Padding doesn't provide any constraints to it's children, The AnalogClock will be taking up all the height and width.

Now since you have given width: 200, the AnalogClick applied a tight constraint horizontally, but still it takes the entire height of the parent. Then, since it needs to scale itself down to 1:1 ratio of height and width, it is appearing in the middle like that.

Just add height: 200, to your clock and this will be the output.

From the outside, it looks like the "analogClock" object needs the "timer" object to exist first, and the "timer" object needs the "analogClock" object to exist first. In reality, thought, "timer" doesn't do anything with the "analogClock" ("clockFrame" inside "ClockTimer"), so it actually doesn't need it.

I'd suggest the following:

1. Remove the "clockFrame" parameter and field inside "ClockTimer"
2. Create the "timer" object first
3. Create the "analogClock" object second, and pass "timer" to it

Its working in my case. Importing these 2 statements.

import 'package:timezone/data/latest.dart' as tz;

import 'package:timezone/standalone.dart' as tz1;

My understanding is that NTVDM (NT Virtual DOS Machine) handles both 16-bit Windows applications and 16/32-bit DOS applications, and is a feature exclusive to the 32-bit (x86) version of Windows not 64-bit (x64).

I found this topic by searching 4001h error via. Google and for me I was able to run my DOS application by launching it via start> run > command.com and then running the EXE as opposed to using CMD or running direct.

Again, this is going to work on the 32-bit version of Windows only. 64-bit version of Windows does not have a command.com command for this to be possible.

I think it would have thrown you an error because you could have not set its constraints.
Try something like this,