@JonB @chatGPT explains the joke in I hear crickets chirping: Excellent question! Let’s break it down clearly and simply. When someone jokes: “C++26 is only 6 more years away before release” they’re poking fun at how long it often takes for compilers and tools to fully support new C++ standards after they are officially published. Here’s the context in plain terms: C++ naming: “C++26” is the standard planned to be finalized in 2026. So the name means the ISO committee is targeting 2026 to finish the standard. But availability lags: Even though the standard is published in 2026, your compiler (like GCC, Clang, MSVC) won’t fully support all its features immediately. Historically it often takes 4–6 years after the standard date for widespread, stable, mainstream support. Examples: C++17 was finalized in 2017, but many people didn’t have fully usable compiler support until ~2020–2021. C++20 was finalized in 2020, but full usable support (including modules, coroutines, concepts) is only maturing around 2024–2025. So when someone says: “C++26 is only 6 more years away before release” they're joking: ✅ The standard will be written in 2026. ✅ But you probably won’t really use it comfortably in production until ~2032.

@cristian-adam said in Qt Creator Android 15 adb.exe pull /system/bin/app_process64 error: I am seeing the same state on macOS with Android 15 and a Samsung Galaxy S23. Thanks for that, yes it seems to be a file access issue, I also wondered if there might be a new Developer Mode setting to enable this to work

Make popup windows modal https://doc.qt.io/qt-6/qml-qtquick-dialogs-dialog.html

Windows Version:Win10 Pro; Pyside6 version:6.9.1 Python File:python-3.11.9-embed-amd64(downloaded from python website,and use pip to install Pyside6) Python Script:import sys from PySide6.QtWidgets import ( QApplication, QMainWindow, QPushButton, QMessageBox ) class MainWindow(QMainWindow): def init(self): super().init() self.setWindowTitle("PySide6 ") self.setGeometry(100, 100, 300, 200) button = QPushButton("Hello", self) button.setGeometry(100, 80, 100, 30) button.clicked.connect(self.show_message) def show_message(self): QMessageBox.information(self, "OK", "OK，PySide6!") if name == "main": app = QApplication(sys.argv) window = MainWindow() window.show() sys.exit(app.exec())

@Shap QPlainTextEdit will (should) behave the same as QTextEdit so far as sizing is concerned. They are both for multiline input, and can grow vertically. QLineEdit is for single-line input, and would not grow vertically. Same as the other widgets you talked about.

Ir seems the @QmlElement decorator is missing (see Tutorial , QmlElement and one example of the tutorial examples.

Hi and welcome to devnet, AFAIK, it literally means that the file path you passed points to something that does not exist. Did you check the path for correctness ? Where does it point to ? What kind of file is that ?

Thanks for the reply! Yes, I agree this really seems to be a tvirt.vir issue, not Qt. That's why I wrote a standalone C program (outside Qt) to test the pipe communication. I’ve already tried: Sending the message DO#0#1 to \\.\pipe\\tubotest Triggering the EventoEnviar event after writing Still, nothing changes on the simulator side, and the input value shown in my DAQ console remains 0. I do have some documentation, and it says tvirt.vir listens for specific commands and events, but I’ll try to confirm exactly what sequence it expects. Thanks again. I’ll keep testing with the C version for now.

@JulsPower That does look more reasonable, i wasn't sure what the MS docs were telling you to do. Which implies you were in the Another possibility is that the issue has nothing to do with Qt or deployment but rather is a "bug" which only happens to show up in certain environments or circumstances. Such as a memory access issue. I had a quick glance at your WTSEnumerateSessionsExA() and it seemed OK to me, but you might want to try it standalone without any Qt stuff to make sure that works across environments. situation! The Qt and deployment changes simply showed or masked the problem. But you have still learnt what you should do to e.g. deploy to another machine, or be sure it works on yours outside of the Creator development environment which should be useful :)

Thank you so much for your support . it works now.

@aha_1980 said in How to switch off specific warnings in Qt Creator: @DiBosco Have you already seen https://stackoverflow.com/questions/22129383/removing-unused-parameters-warning-in-qtcreator ? For your case, it would be: QMAKE_CXXFLAGS_WARN_ON += -Wno-deprecated-copy Regards Ah, yes I had seen that. The English in the most upticked reply just made me go "What?". Just could not understand what they were saying, but I had tried: QMAKE_CXXFLAGS_WARN_ON += -Wdeprecated-copy Thinking why on earth would putting the warning on make it disappear, but out of desperation I gave it a go. Had I realised it needed -Wno-deprecated-copy, not -Wdeprecated-copy I'd've been fine hours ago. Many thanks for that, now doing just what I want. Also @JonB Thanks for your help too.

@J.Hilk said in how to set app-ico ?: shadow build because your not building inside your source file but all generated files are placed in a different folder As @J.Hilk said, I also think the issue is same, image is not in the shadow build folder @cuijg you can uncheck the shadow build checkbox and clean, build, run.

@Mizmas haha, looks funny :)

@J.Hilk thx for the offer... I already did changes - but it's not public yet give me some weeks to publish a first raw Qt 6.9 / CMake release then you can take a look if I missed something ;-)

My full blown test app now runs on the X86_64 simulator it looks awful its ui was not designed for phone use but all the bells gongs and whistles are there and information from my database is populating the widgets which is good. Time now to reflect on what I have learned and tidy up loose ends, thanks to those who helped on this journey.

@SimonSchroeder said in Using QList [] operator in const methods: Even if operator[](int) const returns a copy you have the exact same possible race condition in a multithreading environment. The only advantage is that it is fewer lines of code where this might occur. Multithreading seems an irrelevant point though because the competent programmer understands that accessing a shared resource needs a mutex, so if safe programming processes are observed then there is no race condition. re const vs non-const: totally agree and get it. It's the way things are...however, I do sometimes wish nothing was ever const and everything was mutable. :^)

It's all documented here and it works out of the box. I personally don't use -skip. I explicitly select the submodules I want to build. I always build w/o prefix into directories outside the source tree. E.g. like that: ../dev/configure -developer-build -xcb -nomake examples -make tests -submodules qtdeclarative ninja