QML and Qt Quick

I'm the author of Qml.Net. We use it in production at my workplace. It is strictly a QML integration, so it will work with QtQuick 1/2.

Nope. I like the style and wanted to use a small subset of widgets for an R&D demonstration. At this point, I'm evaluating QT & QML for an augmented reality (AR) head-up display to simplify UI development. The challenge is including a video overlay w/ OpenGL ES processing at 640x512@60Hz. I'm also experiencing issues maintaining a stable 60Hz frame rate, but that's another topic.

Yes, it is possible - but not "supported" and not documented. See this post.

The DeclarativeSurface header file declarativesurface_p.h contains this disclaimer: // W A R N I N G // ------------- // // This file is not part of the QtDataVisualization API. It exists purely as an // implementation detail. This header file may change from version to // version without notice, or even be removed. // // We mean it. From the above, it's pretty clear that the API currently has no supported way of accessing QML Surface3D from C++ - use this class at your own risk. There are no doxygen comments in that file, so user "interpretation" is required to figure out how the methods are to be used. Note that DeclarativeSurface is in namespace QtDataVisualization, but since it's not "formally" a part the API, several additional directories must be specified in INCLUDEPATH; my app's myApp.pro looks like this, where $QT is my QT source directory: INCLUDEPATH += $QT/5.14.2/Src/qtdatavis3d/src/ INCLUDEPATH += $QT/5.14.2/Src/qtdatavis3d/src/datavisualization/global INCLUDEPATH += $QT/5.14.2/Src/qtdatavis3d/src/datavisualization/engine/ INCLUDEPATH += $QT/5.14.2/Src/qtdatavis3d/src/datavisualization/data/ INCLUDEPATH +=$QT/5.14.2/Src/qtdatavis3d/src/datavisualization/theme INCLUDEPATH += $QT/5.14.2/Src/qtdatavis3d/src/datavisualizationqml2 I am developing for a desktop Linux target, and the DeclarativeSurface code is in library $QT/5.14.2/gcc_64/qml/QtDataVisualization/libdatavisualizationqml2.so

Am I using right technique to pass control ID as a string from QML to c++?

@iamRahul I figured it out. We need to specify full location path till the file, and specify file type in format. Then it worked for me. if(audioPlaylist.save("file:///C:/MyMusicPlayer/Playlists/global_playlist.m3u","m3u")) { console.log("Playlist Saved") } Adding the filename global_playlist.m3u and format m3u made it working for me.

Looks like a possible duplicate of this question; https://forum.qt.io/topic/75007/resize-applicationwindow

for now it does work: var content = ddb.loadSection(sectionId) var path = content.path.toString() img.source = path.startsWith("file:///") ? content.path : "file:///" + path I hesitate to mark it as solved since I don't know how dirty it is :-)

I will try again soon. Thanks for the help

Hey @Adso4. You can use this excellent library that saves a lot of work. https://github.com/oKcerG/SortFilterProxyModel Good luck.

Hey.... how did you solved this probleam??. I''m also facing the same issue - white screen. Thanks.

Well I haven't found a way to generate a string literal, but I did find this interesting function of String: String.fromCodePoint(0x1F4A9) It seems to take a utf32 integer and produce the appropriate utf16.

@Vildnex From the looks of your code, it's most likely because you're anchoring it into to the parent.left and parent.rightso it's stretching it across the entire background. THat's probably why it doesn't look like its moving. What I would do is get rid of scrollview and just use Scrollbar inside listview(it inherits from flickable) Here's an example I did for a veritcal listview. ListView { id: settinglist width: parent.width anchors.top: title.bottom anchors.bottom: parent.bottom anchors.horizontalCenter: parent.horizontalCenter boundsBehavior: Flickable.StopAtBounds ScrollBar.vertical: ScrollBar { policy: ScrollBar.AlwaysOn active: ScrollBar.AlwaysOn } model: settingsModel . . . //rest of your code

@fcarney said in Poor quality colored emojis, how to fix that?: font.hintingPreference: Font.PreferNoHinting Wow excellent! This resolved my issue. Thank you very much