Find the Best Demos and Examples

Check out this quick tour to find the best demos and examples for you, and to see how the Felgo SDK can help you to develop your next app or game!

Forums

OverviewFelgo 2 Support (Qt 5) › MouseArea for dragging not supported ?

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #23845

    Luna
    import Felgo 3.0
    import QtQuick 2.5
    import QtQuick.Controls 2.2
    
    App {
        NavigationStack {
            Page {
                title: "Integrate C++ and QML"
                Item {
                    width: 200; height: 200
                    anchors.fill: parent
    
                    DropArea {
                        x: 75; y: 75
                        width: 50; height: 50
    
                        Rectangle {
                            anchors.fill: parent
                            color: "green"
    
                            visible: parent.containsDrag
                        }
                    }
    
                    Rectangle {
                        x: 10; y: 10
                        width: 20; height: 20
                        color: "red"
    
                        Drag.active: dragArea.drag.active
                        Drag.hotSpot.x: 10
                        Drag.hotSpot.y: 10
    
                        MouseArea {
                            id: dragArea
                            anchors.fill: parent
    
                            drag.target: parent
                        }
                    }
                }
            }
        }
    }
    
    Shows the Felgo viewer, but with no contents. When you click around in the background, it sometimes pops up the "buy a license" browser instance
    and kills the app.
    
    How does one drag using the mouse a custom QQuickItem (done mostly in C++)? That is not in the above example, but that is my end goal.
    
    
    
    #23853

    Alex
    Felgo Team

    Hi,

    the issue is a namespace conflict here. Please move the Felgo import as last one, or use a qualified import for QtQuickControls. The root of the issue is that there is also a “Page” type in the QtQuickControls, which conflicts and messes up the UI.

    Best,
    Alex

Viewing 2 posts - 1 through 2 (of 2 total)

RSS feed for this thread

You must be logged in to reply to this topic.