Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. UI not coming up with the usage of the component " MessageDialog"
Qt 6.12 LTS is out! See what's new in the release blog

UI not coming up with the usage of the component " MessageDialog"

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
1 Posts 1 Posters 320 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Y Offline
    Y Offline
    YK1234
    wrote on last edited by
    #1

    Hi,
    I am using Qt 5.15 to develop an UI( QML application) for an embedded device with Yocto Linux.
    The UI doesn't not show up with the usage of "MessageDialog" component. Tried with importing Qt.Quick.dialogs 1.1/1.2/1.3.
    No error related to component or the library is being shown in the logs.

    Configuration:
    OS - Yocto Linux Kirkstone 4.0
    Architecture - ARM architecture
    QT - 5.15 - Custom build of QT for the device.
    Application - QML application

    Please find the code used below:

    import QtQuick 2.15
    import QtQuick.Window 2.15
    import QtQuick.Controls 2.15
    import QtQuick.Dialogs 1.3
    
    Window {
        width: 640
        height: 480
        visible: true
        title: qsTr("Hello World")
    
        Button{
            id: button1
            anchors.centerIn: parent
            width: 100
            height: 200
            onClicked:{
                msg1.open()
            }
        }
    
        MessageDialog{
            id:msg1
             title: "Message"
           text: "Button is clicked !! "
        standardButtons:StandardButton.Ok
        }
    }
    

    Note: When I ran the same QML application on my laptop with Ubuntu 22_04 and having QT 5.15 version installed, it works perfectly fine(UI comes up and Messagedialog is displayed properly without any issues)

    Can anyone please help explain what could be possible cause for this kind of behavior on the embedded device.

    Thanks in advance!

    1 Reply Last reply
    0

    • Login

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Get Qt
    • Unsolved