Cant Interact with QDialog in Qt 6.8.0 ARM64-v8a Android

osos11

Hi,
When I use Qt 6.8.0 I can't interact with anything in the dialog that opens. I think it's mishandling my touch. The dialog is a bit large and I've noticed that as objects multiply it touches a different place than where I touch.
I'm not sure what exactly I need to do or how I can provide more information about this.
Everything works fine with Qt 6.5.3.

Host: Ubuntu 22.04 x64
Kit: Qt 6.8.0 arm64-v8a
Ndk: 27.1.12297006
Java: openjdk version "17.0.12" 2024-07-16
OpenJDK Runtime Environment (build 17.0.12+7-Ubuntu-1ubuntu222.04)
Build-tools: v34.0.0
Build platform SDK: 34
Make: Cmake (Default)

Here is basic example, I cant click or push buttons:

#include "mainwindow.h"
#include "ui_mainwindow.h"
#include <QDialog>
#include <QPushButton>
#include <QVBoxLayout>

MainWindow::MainWindow(QWidget *parent)
    : QMainWindow(parent)
    , ui(new Ui::MainWindow)
{
    ui->setupUi(this);

    QPushButton *openDialogButton = new QPushButton("Open Dialog", this);
    connect(openDialogButton, &QPushButton::clicked, this, &MainWindow::openDialog);

    setCentralWidget(openDialogButton); // Ana pencereye butonu ekle
}

MainWindow::~MainWindow()
{
    delete ui;
}

void MainWindow::openDialog()
{
    QDialog dialog(this);
    dialog.setWindowTitle("Example Dialog");

    QPushButton *button1 = new QPushButton("Button 1", &dialog);
    QPushButton *button2 = new QPushButton("Button 2", &dialog);

    QVBoxLayout *layout = new QVBoxLayout(&dialog);
    layout->addWidget(button1);
    layout->addWidget(button2);

    connect(button1, &QPushButton::clicked, &dialog, &QDialog::accept);
    connect(button2, &QPushButton::clicked, &dialog, &QDialog::reject);

    dialog.setMinimumSize(250, 150);
    dialog.exec();
}

Aaron Liao

Yeah, I've met the same problem, and I found that QPrintDialog also doesn't support interaction on Android.

Aaron Liao

@Aaron-Liao My android version is 12

osos11

@Aaron-Liao
Check this: https://bugreports.qt.io/browse/QTBUG-130576

I have created a bug report for this issue.