Unless clipping is enabled, `paintedWidth` and `paintedHeight`
provide more information on the actual region that the source
item rendered content.
These properties are provided in `QQuickImage`. However, it is
not necessary that the type is `QQuickImage`. We should respect
each type that provides such information.
The docs state that:
> Note that INI files lose the distinction
between numeric data and the strings used
to encode them, so values written as numbers
shall be read back as QString. The numeric
value can be recovered using QString::toInt(),
QString::toDouble() and related functions.
Currently, double-precision numbers can not
be reconstructed properly due to QString's
way of handling dp numbers.
Since they are read back as QString, we
should save these numbers according to the
precision that QString is comfortable with,
so that they are parsed properly when the
application starts.
Under some circumstances, the application won't close after a quit event.
Using an `exit` in `triggerQuit` callback ensure that the application won't
prevent the mainloop to quit. At this point, both the gui and vout are stopped
Windows 11 identifies as Windows 10 (NT 10),
so this comparison always yields false.
As a side note, native acrylic background
for Win32 windows only gained support with
the Windows 11 22H2 update, that's why
there is the check here.
Note that according to the general conventions
a transparent window must be frameless on
Windows. This is currently not the case,
because "frameless window don't support
areo snapping". So, it can be considered
as a known bug if native acrylic does not
work as intended. This grants a requirement
of change to use frameless window, and get
rid of the current workaround that simulates
frameless window in mainctx_win32.cpp. If
aero snapping does not work, it is Windows's
problem since we are using frameless windows
in every other platform.
scoping and generic name of root grid item of this view
was causing invalid object access in this view
fix: use direct parent as reference for size
NOTE: changing the name of parent grid item also fixes this issue