Getting this weird error everytime I use cool-retro-term.

$ user@host ~ ❱ ✔ ≻ cool-retro-term
WARNING: CPU random generator seem to be failing, disable hardware random number generation
WARNING: RDRND generated: 0xffffffff 0xffffffff 0xffffffff 0xffffffff
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.

$ user@host ~

My printer displays the Z height. Cura displays the layer number. When editing Gcode it would be nice to have the Z height displayed along with the Layer number in the little text box at the top of the preview slider. It would also be nice if the layer number in Cura was the same as the layer number in the Gcode file that Cura generates. Right now Gcode layers start at "0" and Cura layers star

The current CONTRIBUTING.md is more like a CODE-OF-CONDUCT.md. Which is good because now we don't have to figure out one by ourselves 😁

The CONTRIBUTING.md should only contain details for developers and non-developers on how to contribute to the project.

For devs this would mean a technical guide on how to set up the environment and a narrow explanation on which directories of the p

The lack of documentation is surprising, I'm new to all of this so It confuses me alot how to even beginn a project.
Could someone have a look and verify which modules need to be installed for a minimal Qml.Net to work, And add this to a wiki?

Additional Questions:
Does Visual Studio need all these C++ dependencies if QT have them?
Is there a way to simple choose between MSVC and MinGW

I cannot find neither in man pages nor here in github how to switch to another graphical session (second user). How do I switch and switch back?
I'm using Lubuntu 19.10, not KDE desktop, but the Lubuntu desktop itself. So I do not have the practical and very useful dm-tool command from lightdm. Nor there is a script to switch, something like lxqt-switch or sddm-switch. I have asked in Lubuntu.me

I tried to run tests on Win 10, nvm 8.11.1:
C:\Users\BeSSoRioN\Documents\GitHub\qmlweb>npm run test

Result output you can see below. remark command return exit status 1 because of warnings, so test procedure fails on remark -qf *.md docs:

> qmlweb@0.2.0 test C:\Users\BeSSoRioN\Documents\GitHub\qmlweb
> npm run lint && gulp test

`> qmlweb@0.2.0 lint C:\Users\BeSSoRi

To make typography legible on top of imagery, apply text protection in the form of scrims. Scrims are lightweight, translucent material layers.

Text protection from https://material.io/guidelines/style/imagery.html#imagery-best-practices

in example topolopy, when i execute "clear Graph", the message show "TypeError: Property 'clear' of object qan::FaceGraph_QML_70(0x7884400, "graph") is not a function",so i modify "void clear() noexcept;" to " Q_INVOKABLE void clear() noexcept;" in the file "qanGraph.h" 103 line ,but that still error.

• Operating system and version: Windows 10
• YubiKey model and version: Yubico Authenticator 5.0.2
• Bug description summary: Looks like Qt problem

Steps to reproduce

1. Show in System Tray checked.
2. Right click on system tray icon.
3. Menu popout visible.
4. Trying to close menu (without success) when click away.

Expected result

Menu hides when clicking away

Actual res

按wiki的方法构建动态库,在使用TToast组件时出现以下异常:
qrc:/net.toou.2d/controls/TToast.qml:101: TypeError: Cannot read property of null

First off I just want to say that the theme tutorials are very detailed and educative! Kudos for that!

Would it be possible to get an update regarding the changed API reference in the theme creation tutorials? I've tried to figure out what the differences are with the updated API, but it feels like some of the new practices aren't explained. I'm especially having trouble with changing and getti

If multiple features are adjacent, a single touch will identify several of them.
A way to control this behaviour would be extremely useful.

The current behaviour offers no control and makes feature identification imprecise.
If several adjacent polygons are present in the layer, a single touch will identify all of them.
After that, the desired polygon must be selected from the list.
It would

Add to documentation to particular component information about it's inheritance tree (e.g. WebItem->Rectangle->Item), so inherited properties and methods can be easily accessible.
Having kind of inheritance structure would be nice:
"interits": {
"name": "Rectangle",
"ref": "core/Ractangle",
"inherits": {
"name": "Item",
"ref": "core/Item",
"inherits

On Windows, if you are building with mingw, instead of using the make command, use mingw32-make.
fyi ... this is a helpful plugin, thanks.

Our install instructions are missing crucial things (#40) and can be more detailed about how to install on specific OSs.