@jsulm Yes I have made the structure like this, but did not know how to use. I will try this. I am posting previous code below so that can I get better feedback , if made silly mistakes in it. I will explain the process below this code with picture mainwindow.h file #ifndef MAINWINDOW_H #define MAINWINDOW_H #include <QMainWindow> #include <QUdpSocket> typedef struct{ unsigned short header; unsigned char diData[8]; }test; QT_BEGIN_NAMESPACE namespace Ui { class MainWindow; } QT_END_NAMESPACE class MainWindow : public QMainWindow { Q_OBJECT public: MainWindow(QWidget *parent = nullptr); ~MainWindow(); private slots: void connection(); void on_pushButton_clicked(); private: Ui::MainWindow *ui; QUdpSocket *socket; QHostAddress host_address; quint16 host_port; }; #endif // MAINWINDOW_H Mainwindow.cpp file #include "mainwindow.h" #include "ui_mainwindow.h" #include <QHostAddress> #include <QDebug> #include<QByteArray> #define localaddress QHostAddress("192.168.1.167") #define port 5000 test test_data; MainWindow::MainWindow(QWidget *parent) : QMainWindow(parent) , ui(new Ui::MainWindow) { ui->setupUi(this); host_address= QHostAddress("192.168.1.167"); host_port=1234; socket = new QUdpSocket(this); socket->bind(localaddress, port); connect(socket, SIGNAL(readyRead()), this, SLOT(connection())); } MainWindow::~MainWindow() { delete ui; } void MainWindow::connection() { while(socket->hasPendingDatagrams()) { QByteArray datagram; datagram.resize(socket->pendingDatagramSize()); QHostAddress sender; quint16 senderport; socket->readDatagram(datagram.data(),datagram.size(), &sender, &senderport); QString message = datagram.toHex(); qDebug() << message; qDebug() << size; } } so this was basic code to get the UDP data. Now I am sending 10 bytes from hercules. You can see I am getting the whole data in the Qdebug but how do i get that into my structure , That my point.

Ok. I've found example of CMakeLists.txt in Qt6 repo. it works if apply all sources of sub-item to main executable like qt_add_executable(chapter1-basics main.cpp piechart.cpp piechart.h ) but is there way to separate sub-item as external library ? something like a qt_add_executable(chapter1-basics main.cpp ) ... qt_add_library(lib_piechart piechart.cpp piechart.h) target_link_libraries(lib_piechart PUBLIC Qt::Core Qt::Gui Qt::Qml Qt::Quick) target_link_libraries(chapter1-basics PRIVATE lib_piechart)

You can simply catch all unhandled click events below your inputs. Please note if you apply anchors.fill to the TextInput and the TapHandler has the same clickable area, all click events will stay in the TextInput as it covers the entire area of the TapHandler. Compare to the example below with the Rectangle indicating the area of the TextInput. Item{ id: contentWrapper anchors.fill: parent TapHandler{ id: clickOutsideCatcher onTapped: { console.debug("catched click outside") // this removes the active focus from the input field contentWrapper.forceActiveFocus() } } Rectangle{ id: highlightTextInputArea anchors.fill: num_id color: "red" } TextInput { id: num_id text: "1234" font.pixelSize: 20 selectByMouse: true //anchors.fill: parent validator: IntValidator {bottom: 1; top: 100000} } }

@pingal said in Defining FD_SETSIZE in .pro file: In the compiler output, it is shown as "-DFD_SETSIZE=1500" Which is correct, so you should search the error elsewhere, it's not that the macro isn't defined or has the wrong value. Probably this simply isn't supported anymore (as it appears to be some sort of legacy quick-fix).

@invalidipnan I would also suggest, not using the release candidate of the SDK build tools but rather a stable one.

@Swati777999 The Qt tool chain, similar to others, has a bunch of code generating tools that are run during a compilation. Above all the Meta-Object Compiler (MOC). If you don't shadow build, all those files will clutter your source directory. And being the smart as tools that they are, they will not regenerate files, that already exist, if "nothing changed" The problem now, is that detection is not 100 % reliable, especially if you switch between debug/release builds and/or compilers Something similar happened in your described situation. The go to tool is a clean rebuild, aka rerunning qmake/cmake or simply deleting the shadow build folder. don't uncheck the shadow build checkbox, you'll invite problems later down the line, if you have to change it select an other path/directory to shadow build in, it will have the same effect.

@Strilles Have you checked your usage of {}? I don't know here, but they are used for "match-counts" in, say .{2,4}. Did you try escaping them, \{\}?

@Ulatekh said in Browsing the Qt source in an IDE?: FYI, I'm doing this under Fedora Core 35. Compiler version is more important in this case. PS: ../qt5/configure -developer-build -opensource -nomake examples -nomake tests You'd want to run this directly from the source tree with Qt5.

@MScottM said in qml function in Qt6: Item { id: readlistValues function readValues(anArray) { for (var i=0; i<33; i++) //console.log("list: ", anArray[i]) label0Text = anArray[0] //snip... label33Text = anArray[33] } } anArray[33]? Are you sure you have so many elements? Also I'd very much question the wisdom of having a million of these things: labelXXXText. "Parameter "lblMsg" is not declared. Injection of parameters into signal handlers is deprecated. Use JavaScript functions with formal parameters instead." Connections { target: modfinder onSetModule: { modFinder.setModule(lblMsg) } } modFinder vs modfinder, also lblMsg isn't defined, specify explicitly through an object id. Is this property part of the target? Perhaps it's supposed to be: modFinder.setModule(modFinder.lblMsg)

Okay I figured this out. By searching the whole Qt source tree for "XCB GLX" I found this rule in qtbase/src/gui/configure.json which seems to be what causes the build check to be skipped. "xcb-glx-plugin": { "label": "GLX Plugin", "emitIf": "features.xcb", "condition": "features.xcb-xlib && features.opengl && !features.opengles2", "output": [ "privateFeature" ] }, In my case xcb-xlib being missing was the failing condition. By adding -xcb-xlib to the configure options, I could force configure to run the checks, and then resume my earlier procedure of looking at config.log to see details about what failed, and then copying the missing headers/libs into the target toolchain (libxcb-xinput.so in this case). The reason libxcb-xinput.so did not exist is because I was copying in libs and headers from Ubuntu 16.04, which simply does not have libxcb-xinput. Fortunately I was able to build that from source easily enough.

Hi and welcome to devnet, QStackedWidget does not care nor handle what do the widgets inside it. What will not happen is UI updates but all the rest will. What you can do is disable these processing when the widgets are not visible if it makes sense.

@ChrisW67 It isn't, and I wondered about that, but these days one doesn't dare to ask when OPs state it is "obvious" what it is and/or did not paste their actual code but you should guess what it really is..... @ocgltd qDebug() << rowsAffected; Is this your actual code? rowsAffected is what --- an undeclared local variable, an unset member variable? There is a int QSqlQuery::numRowsAffected() const, but you don't show any call to it?

@AnneRanch You have asked this so many times, and been answered. You cannot execute hcitool -i hci0 scan --flush | tee /tmp/temp as the command in process ->start(command). The answer is always the same: process ->start("/bin/sh", QStringList() << "-c" << command); YES, I can go back to passing data to "bash"... BUT bash script does not accept some standard options likes "|" and "tee". Completely incorrect. It is only either /bin/sh or /bin/bash which does accept and interpret |. tee has nothing to do with the shell, and works fine from either. If I do pass QSTring to QPProcess - what is the corrent systex for passinf "system" function ? There is no system-anything to pass to QProcess. system() is an alternative to using QProcess. You are better using QProcess in Qt programs and not system(). There is nothing system() does that QProcess() cannot do, but there are things you can do with QProcess which cannot be done with system(). You could save yourself time but not trying to use system(), I have shown you the equivalent process ->start() to use instead. Which one of QProcess standard SIGNALs should I monitor for possible error? void errorOccurred(QProcess::ProcessError error) errorOccurred() is the signal for errors launching QProcess. You will doubtless be interested in other things which happen that are not process errors, even if you might think they should be. They may be reported by reading stderr (readyReadStandardError()) and possibly stdout too. For the simplest case just use const char *command = "hcitool -i hci0 scan --flush | tee /tmp/temp"; process ->start("/bin/sh", QStringList() << "-c" << command); process->waitForFinished(); qDebug() << process->readAllStandardError(); qDebug() << process->readAllStandardOutput(); You should also connect on the errorOccurred signal, just in case.

@James-A Do you not think this is an internal GDBserver error?

@andi456 That's fine, QStyledItemDelegate seems best. What triggers the paint method of QStyledItemDelegate? Just whenever it needs painting/re-painting! QStyledItemDelegate receives a QModelIndex(). That contains the row. You can find the "column x" with the desired color via siblingAtColumn() in the row.

@dev_liya said in I want to generate random number between the 0 to 1. with the interval of 1 second in qt.: but my requirement is to generate in infinite loop ad show in window. If you do an infinite loop then the event loop will not run. That means that setting the random_label or anything like that will not show on the screen as the slots cannot be handled: your infinite loop will block the event loop. The effect is that you have a frozen application. So, trust @JonB. As per your request: to wait for one second and block everything (you have been warned!): use QThread::sleep(1);

@harish__rajora Found this: https://forum.qt.io/topic/41943/platform-plugin-windows/8 Check the last post there.

@SGaist it seems that the customer(designer) has designed the screens with the look&feel that they want. At least that seems to be the case for the "looks like" setup I saw on Tuesday...i've used Qt a few times in the past (2015&2017...v4.8), but it was all Qwidgets...never had to process x&y pixel locations...i did that kinda thing around 1985 or so...HP Apollo workstation running Aegis/DomainOS/UNIX-like...back then I mapped the entire 1280x1024 screen...buttons in the 256x1024 area on the right and 1024x1024 air situation area on the left...COTS system for an air traffic control contract bid while working for a DOD contractor...in my day...lol....Now if the customer designer wants his png slides to come to "life" behind the touch screen, can I just map the 720x1280 screen using a 2 dimensional array with a unique Number for the GUI items on the png image...do a switch case on the Number and process accordingly...will have to have a QTextEdit/LineEdit/PlainTextEdit...to display/delete the entries from the small keyboard, etc...Plus i got some circular progress bars i will have to create...that may require some "image slicing"...what's your take/thoughts...Thanks!!!

The detailed description should help here. Create timer, connect timeout to the your custom slot, do your work and checks in there.

@AnneRanch said in How to read "enum" using debug ?: (int result , enum QProcess::ExitStatus) Basics: You don't define a variable for QProcess::ExitStatus so you can't access it.

@IknowQT Why you need stylesheet when you use the paintEvent anyway? How does your paintEvent look like? Do you call the base implementation of QPushButton::paintEvent afterwards? It could overwrite your custom style

Hi, One thing you might want to explore is QAbstractFormBuilder.

Assuming that you have done the obvious stuff like looking at the debug output for any runtime messages, I usually find that when things are not appearing that it is some sort of layout/positioning/sizing issue, rather than a specific error in using the component. It's not very well advertised but GammaRay can be a useful tool for debugging this sort of issue.

@James-A I think you could simply copy the default styling to your project and modify it. Here you can modify anything (font size, font family, colors, keyboard size, replace images, etc.). QtQuick/VirtualKeyboard/Styles/default/ // apply your style in main.cpp qputenv("QT_VIRTUALKEYBOARD_STYLE", "yourStyleDirectoryName"); qputenv("QT_VIRTUALKEYBOARD_LAYOUT_PATH", "qrc:/path/to/your/style/directory/from/above");

Please also note that there's a 'New to Qt' section, both on https://doc.qt.io , and at the end of https://doc.qt.io/qt.html .