Skip to content
Brand Logo
  1. Home
  2. Qt Development

Qt Development

Everything development. From desktop and mobile to cloud. Games, tools, 3rd party libraries. Everything.
144.1k Topics 720.6k Posts
Forum Updated to NodeBB v4.3 + New Features

Subcategories

  • This is where all the desktop OS and general Qt questions belong.
    83k 456k
    83k Topics
    456k Posts
    W
    Refer to these classes for <QCamera>、<QCameraViewfinder>、<QCameraImageCapture>, which should solve your problem

  • The forum for developing everything embedded: Linux, WinCE, Symbian, MeeGo... you name it.
    14k 62k
    14k Topics
    62k Posts
    KenAppleby 0K
    @KenAppleby-0 Correction: a simple test app does show the symptoms - displaying outside the safe areas. A full clean removal of the build directory and CMakeLists.txt.user and a fresh build and it is consistently showing the behaviour: the child widgets are drawn outside the safe areas. The simple test app is below. It's confusing, because the same code, when rebuilt from scratch, can sometimes behave correctly. I have not been able to work out what the different results are caused by. #pragma once #include <QWidget> class SafeAreaTestWidget : public QWidget { Q_OBJECT public: SafeAreaTestWidget(QWidget *parent = nullptr); ~SafeAreaTestWidget(); }; //////// #include "safeareatestwidget.hpp" #include <QVBoxLayout> #include <QLabel> #include <QLineEdit> #include <QTextEdit> #include <QTextBrowser> SafeAreaTestWidget::SafeAreaTestWidget(QWidget *parent) : QWidget(parent) { QVBoxLayout * layout{ new QVBoxLayout{ this } }; QLabel * label{ new QLabel }; label->setText("Safe Area Test"); QLineEdit * lineEdit{ new QLineEdit }; QTextEdit * textEdit{ new QTextBrowser }; textEdit->setReadOnly(false); layout->addWidget(label); layout->addWidget(lineEdit); layout->addWidget(textEdit); setStyleSheet("QLabel { background-color: #880000; } * { background-color: #8888ff; }"); } SafeAreaTestWidget::~SafeAreaTestWidget() {} ////////// #include "safeareatestwidget.hpp" #include <QApplication> int main(int argc, char *argv[]) { QApplication a(argc, argv); SafeAreaTestWidget w; w.show(); return a.exec(); }

  • Looking for The Bling Thing(tm)? Post here!
    20k 77k
    20k Topics
    77k Posts
    R
    I'm new to Qt. I'm learning the official document Getting Started Programming with Qt Quick. When I run this example with give codes on my PC. The Main window does not show the "Repeat days" buttons. Please see following pictures. My OS is Windows10, Qt version is 6.9.0, Qt Creator version is 16.0.2. The codes can be found here. Please help me, thank you. [image: fe171605-ee6c-4d3c-8079-3c1d9747b0fd.png]

  • Have a question about Qt Creator, our cross-platform IDE, or any of the other tools? Ask here!
    8k 35k
    8k Topics
    35k Posts
    C
    Hi , everyone~ In Qt Creator 16.0.2, any breakpoint you set before starting the debugger is hit as expected. However, if you try to add a new breakpoint after the application is already running the IDE marks it but it never becomes “active” and won’t be hit (and can even cause the debugger to hang when setting it). What I’ve Tried Start debugging with a breakpoint on MainWindow::~MainWindow() → hit OK. Once running, click in the margin at QApplication a(argc, argv); to add a new breakpoint → turns red/grey but never activates. Stop & restart with that breakpoint set before launching → it works perfectly. This happens identically in: Qt 5.15.0 project (GDB 11.2.0 + MinGW 8.1.0) Qt 6.9.1 project (GDB 13.1.0 + MinGW 13.1.0) Image 1: Breakpoint on MainWindow::~MainWindow() (set before run) is recognized and hit. [image: 8433057d-b1e2-409f-a950-5985043747d8.png] Image 2: Breakpoint on QApplication a(argc, argv); (added after run) turns grey and never hits. [image: 5693685d-e846-45a3-9205-d3a94126d411.png]

  • Your Qt just doesn't want to build? Your compiler can't find the libs? Here's where you find comfort and understanding. And help.
    10k 51k
    10k Topics
    51k Posts
    JKSHJ
    @ZergedU said in Cannot run Qt Online Installer on Red Hat UBI 9, libxkbcommon-x11.so.0 missing: It looks like Red Hat UBI 9 strips down the AppStream repo from the RHEL version. Notably, the package "libxkbcommon-x11" is missing. Ah... that's a shame. I guess you'll need to resort to a 3rd-party repo then? (Or build it from source)

  • What can we say - we like games. And you can use Qt to write some. Questions? Ask here.
    869 4k
    869 Topics
    4k Posts
    BondrusiekB
    @EndrII-0 , sure! you can.(will be very great if you also share a source code)

  • Questions about Qt WebKit and related topics? Post here!
    2k 6k
    2k Topics
    6k Posts
    JonBJ
    @Vbrg So in a word Qt only offers integrated browser with chromium/Qt web engine.

  • Discussions and questions on QtWebEngine
    1k 4k
    1k Topics
    4k Posts
    A
    Hello, @raphm01 Doyou resolve your problem? I have similar issue with terrible flickering of Webpage when using PyQT6 on windows OS

  • You're using Qt with other languages than C++, eh? Post here!
    864 3k
    864 Topics
    3k Posts
    PedromixP
    Brand new release QtJambi 6.9.1 is out now🥂. Create sophisticated Java apps for Desktop and Mobile or refactor your legacy code using Qt as UI framework! https://www.qtjambi.io [image: cb78556c-b761-467b-b005-119e3643175c.png]

  • Combining Qt with 3rd party libraries or components? Ask here!
    1k 6k
    1k Topics
    6k Posts
    Axel SpoerlA
    @Dream_Helium said in Using Qt Program as a Module, but constantly get critical message: using GModule to load a Qt module just that thought scares me! Which Qt module are you loading and why with GModule? What is the expected result? g_main_context_pop_thread_default: assertion 'stack != NULL' failed As rightfully said: That error message comes from glib, not from Qt. Maybe consult the gtk forum.

  • For discussion and questions about Qt for Python (PySide & Shiboken)

    3k 14k
    3k Topics
    14k Posts
    CristianMaureiraC
    Externally, no, but you can always follow the meeting notes: https://wiki.qt.io/Qt_for_Python_Development_Notes you can see iOS support is being actively investigated.

  • Specific issues when using Qt for WebAssembly

    454 2k
    454 Topics
    2k Posts
    MesrineM
    If I remember well, this SharedArrayBuffer is needed when using wasm multithreading. If your app does not need multithreading, use Qt wasm single threading. If multithreading is needed, check https://forum.qt.io/post/765010

  • Discussions and questions about Qt Quick Ultralite and using Qt on microcontrollers in general

    141 438
    141 Topics
    438 Posts
    S
    Hi, Thank you so much for taking the time to respond — I really appreciate it. Yes, I have previously tried using the qmlprojectexporter from Qt for MCUs 2.8.2 while keeping the rest of the toolchain and setup on 2.7.1. The project compiles successfully with that approach. However, even with the 2.8.2 exporter, I did not observe any noticeable reduction in the generated font file size. The memory usage for qul_font_engines.cpp remains almost the same, which is the core issue I'm trying to address. Thanks again for your input — happy to hear any further ideas you might have!

  • The forum for discussing the Qt Digital Advertising Platform

    17 41
    17 Topics
    41 Posts
    E
    @nayka Can I use QtDigitalAdvertising on PC applications? Or is it only allowed for use on Android or iOS mobile devices?

  • For discussion and questions about Qt Insight

    10 15
    10 Topics
    15 Posts
    jsulmJ
    @Alejandro_qt_ Not clear to me: did you manage to compile and install this Qt module with your changes and only debugging doesn't work properly? Or you can't compile that module with your changes?