If I understood correctly, you want to draw a red line.
The purpose of Path is to position elements through a path. Think of a row or a column that's not straight. You can understand better if you run the first example from this tutorial.

To draw paths you need Shape.

import QtQuick 2.15 import QtQuick.Window 2.15 import QtQuick.Shapes 1.12 Window { width: 640 height: 480 visible: true title: qsTr("Редактор персонажей") Shape { ShapePath { strokeColor: "red"; // it works :) startX: 0; startY: 100 PathLine { x: 640; y: 480 } } } }

@timob256 I entered "Qt Quick draw line" in Google and got this: https://doc.qt.io/qt-5/qml-qtquick-pathline.html

Problem solved by calling chekbox.forceActiveFocus(Qt.TabFocusReason)

@Phips04 Your welcome

I found out that between two cases (working and not working one) only file that differs substantially is qmlcache_loader.cpp. In non-working case it was over 5 times smaller than normally, and that's because 80% of all resources were not there.

Now, the only reason why it's happened is because some qrc files has been added to RESOURCES twice, and only those resources were available at the end.
Why it worked after moving file from one qrc file to another? Probably because only those part of the project which depends on that two files has been updated and though every qrc file has been included only once (duplicates was in my case in the other part of the project).

EDIT:
Before marking it as solved I will try to confirm all of the above hypothesis.

It does look like a similar issue. I was able to find a workaround thanks to this bug report. Setting the target OSX version to 10.12 in CMake did the trick.

@GrecKo oh thank you very much. I confused bottomMargin for anchors.bottomMargin. I wasn't aware of this property being available. This is exactly what I needed!

@Angelking 恰好我也在做这方面的研究。
我的需求是，为我们的动作编辑器增添Direct3D的支持，因为用户更加习惯MME----这是一个基于HLSL的渲染框架。
这里问题在于我们使用的是Qt Quick，而现有的代码是和OpenGL深度绑定的，我们需要做的是考察哪些地方和OpenGL深度绑定的，然后尝试抽象出来，做好做成一个插件，我是考察Qt插件的写法决定将OpenGL相关的内容放在插件里实现。

想让Qt Quick应用和OpenGL和Direct3D解耦，我想一个方法就是使用RTT技术。就是采用不同的渲染器在一个纹理图上渲染，这样有可能通用。但是其中的难点感觉还是挺多的，现在在艰难地攻克。

After some tinkering, I've gotten the designer plugin to work the way I originally wanted. I simply commented out the 'module' directive in the 'qmldir' file:

# module MyLib typeinfo plugin.qmltypes plugin MyLib ../ designersupported

and added some qmake targets to automatically run 'qmlplugindump' post-build.

So now my plugin directory structure looks like this:

/imports |---MyLib.dll (or libMyLib.so) |---/MyLib |---|---qmldir |---|---plugin.qmltypes

Now I can get the plugin to run in 'qmlscene':

qmlscene -I <imports directory> <main qml file>

There are only two caveats in this case. First, QML files that are to import anything from the library must first import 'MyLib 1.0' before importing anything else ('MyLib.Rectangle', 'MyLib.Circle', etc.). This is so that the plugin is loaded initially to populate the other imports. Secondly, this will produce the following message when the plugin is loaded:

Module 'MyLib' does not contain a module identifier directive - it cannot be protected from external registrations.

However in my case, this is not an issue and can be safely overlooked.

@dv__ said in QML animations with dynamic content:

Also, just out of curiosity, in a more generic case (say, some arbitrary, non-grid arrangement), would my approach make sense? I suppose I could still use ListModel in this case, but the arrangement would have to be done manually, not with an existing view.

To do this I'd use a raw Item container with a Repeater and manual positioning in the delegates.

@GrecKo thanks for your comment. I've managed to create the window in which people would touch the video, but I'm not sure how to make the player. I've seen there is a library, Qt media, but I don't really know how to bind it with the other screen.

You have to enable Use QML emulation layer that is built with the selected Qt in the settings, since Qt Creator does ship with Canvas3D.
Note that Canvas3D is not officially supported in the designer, though.

Thanks @jpnurmi,

This is exactly what i was looking for, all my issues are solved.

Hi and welcome to devnet,

Why not free anymore ? Looks rather like a licensing issue. LGPLv2.1 has been replaced by LGPLv3.