As a follow-up to my previous post, I’m sharing a short technical overview document of PlugFrame for developers interested in the project architecture and design approach. Technical overview PDF: https://github.com/ELEKDOM/PlugFrame/blob/master/docs/ELEKDOM_PlugFrame_overview.pdf Best regards, Christophe

you should use an ApplicationWindow: ApplicationWindow { width: 640 height: 480 visible: true title: qsTr("Hello World") flags: Qt.Window | Qt.ExpandedClientAreaHint | Qt.NoTitleBarBackgroundHint and play around with code like this: background: Rectangle{ color: "red" // "#cfcfcf" anchors.bottom: parent.bottom height: parent.height + SafeArea.margins.bottom } -- background: Rectangle{ color: "red" // "#cfcfcf" anchors.bottom: parent.bottom height: parent.height + SafeArea.margins.bottom anchors.bottomMargin: SafeArea.margins.bottom } Learn more about edge-to-edge windows and Qt SafeAreas from here or take a look at my test application.

I have also tried taking the implementation directly from the TextField.qml file from the Material Style which results in this behaviour: As you can see it is always visible and doesnt "make space" for the placeholder Text. [image: b2db065a-f2c8-4034-ae8d-79309d4fc7b3.png] Component { id: enabledBackground MaterialTextContainer { implicitWidth: 120 implicitHeight: control.Material.textFieldHeight filled: control.Material.containerStyle === Material.Filled fillColor: control.Material.textFieldFilledContainerColor outlineColor: (enabled && control.hovered) ? control.Material.primaryTextColor : control.Material.hintTextColor focusedOutlineColor: control.Material.accentColor placeholderTextWidth: Math.min(placeholder.width, placeholder.implicitWidth) * placeholder.scale placeholderTextHAlign: control.effectiveHorizontalAlignment controlHasActiveFocus: control.activeFocus controlHasText: control.length > 0 placeholderHasText: placeholder.text.length > 0 horizontalPadding: control.Material.textFieldHorizontalPadding } }

Ich entwickle eher selten unter Linux und kann dir keine direkte Antwort darauf geben. Allerdings kannst du das im Qt Creator selbst herausfinden: In den Einstellungen findest du deine "Kits". Dort kannst du nachschauen, in welchen Pfaden denn Qt Creator die Qt Bibliotheken findet.

The clicked() signal is usually for the left click. However, for QWidgets you can setContextMenuPolicy() to Qt::CustomContextMenu. Then you should connect to customContextMenuRequested(). This signal will even give you the position where to show the context menu.

@SGaist Why ? I use gnome. What is the different ?

The bindings for QtOpcUa, QtMqtt and QtCoap are provided for commercial license owners as part of the commercial offering. So, the contribution can unfortunately not be accepted.

@Jacek-Marcin-Jaworski said in forum.qt.io edited posts shows badly in elinks browser: When I display forum.qt.io posts in elinks browser, then it shows me historical version of edited posts. Good example is that thread, where three top posts were edited and appear as 6 posts! The thread that you linked does not contain ANY edited posts, as far as I can see. Do you mean quotes, rather than edits? Please fix it. Thank you in advance! The content layout is done by NodeBB, so all NodeBB-based forums would likely produce the same results. I'd suggest discussing this at https://community.nodebb.org/ and/or the ELinks project instead.

@JoeCFD said in Vibe coding / AI code generation for Qt based applications: As of late April 2026, SpaceX has secured a deal with the option to acquire AI coding startup Cursor (Anysphere) at a $60 billion valuation later in 2026. Qt has QtCreator and can easily add any AI engine. What a loss of opportunity! What opportunity are you talking about ?

@galkinvv Thanks for your workaround for this. It got me up and running. According to this We should be able to use mount-libexec and libexec-mount-point for this. However, I tried them and they don't work. Have you found out anything more about this? Kevin

Thank you both @Christian-Ehrlicher , @Kent-Dorfman ! I changed it and now it no longer runs on Wayland and it renders in the middle :)) This was so helpful! Thanks again!

[Using QtCreator 18.0.2 and Qt 6.7.2] I had the same issue and I solved it by adding "NO_CACHEGEN" under "qt_add_qml_module" in my CMakeLists.txt file. As far as I understand, this problem occurs because the Preview uses the file under build folder but your changes occur on your projects file (which are not exactly the same file) and this tag disables caching and thus solves the problem. qt_add_qml_module(appXXX URI XXX VERSION 1.0 NO_CACHEGEN

Oh, a post on April 1st.

@hskoglund Using a timer can be anything between a waste of time and vain hope. It depends on the operating system, how showMaximized(), showNormal() and the like are handled. QWidget::windowState() reflects what has been ordered to the window manager. The problem is that the widget's geometry can change twice. First time when showMaximized() has been processed and widget->windowState().testFlag(Qt::WindowMaximized) returns true. Second time, when the window manager has applied decorations (i.e. title bar and window handles). A good place to look for inspiration is tst_QWidget::showMaximized() and showFullScreen(). The QTRY_ macros generally process events until either the predicate is true or a timeout is hit. They're not available in applications, but you can write your own methods that work for your use case.