Ah, yes, those JS quirks. Been hacking with Python, where None as a key is
completely legal.
Object.keys(o).forEach((k)=>{console.log(typeof(k));}); would have told me I
was in error.
Interesting confluence of things:
JS console does not print the keys as string:
> var a = {a:1, b:2, undefined:0
The key is always a string into named array, so you undefined key is transform
(optional quote there for JS which is lazy and useless rule) into "undefined"
string literal.
What you want to do is a prototype or a function that will verify this for you:
function dictKey(dict, key, defaultKey = "
Simplified example:
Text {
property var textForColor: {"transparent": "Waiting", "lime": "Ready",
undefined: "Initializing"}
text: textForColor[color]
color: // set somewhere else, potentially undefined at the start
}
But if I include the undefined key, QML complains.
Fails execution
Hi,
I have an issue on a computer running KUbuntu 19.10.
Basically the issue is that Qt does not handle properly the font weights.
For instance for "Ubuntu Mono" I have the Regular and Bold fonts installed
and they are properly registered in fontconfig:
fc-match "Ubuntu Mono"
UbuntuMono
Thanks for reply! Time to rewrite the Build Scripts again. Well not
before late Summer - maybe the Major Stuff has been decided upon by then.
Oliver
Am 02/01/2020 um 08:34 schrieb Maurice Kalinowski:
> Hi,
>
> The Cmake branch readme contains this section:
> https://code.qt.io/cgit/qt/qtbase.gi
