General and Desktop

The *_p.h files are the declaration of a private implementation, PIMPL, of the related class e.g., qlocale.h and qlocale_p.h. PIMPL is used for varied reasons, for example: Make maintaining binary compatibility across versions easier. So, for example, code written and linked against Qt 5.12 can use a Qt 5.15 library set even if the internal implementation of some classes is wildly different. Make implementation opaque, with only a public API header published with a binary library. Qt does both. Have a read here for example.

@SGaist I changed the desing: Now QPushButtons are displayed in the QScrollArea, so the Button with the ssid and the other elements (The line to write a password, the button to connect to a network) are shown separately. With these simple changes, the code I wrote before works like a charm! True, It wasn't what I originally intended, but I realized that it's far better due to the circumstances where this app is going to be used. Thanks for your time and your help!

Find pid of any running TestApp and kill it first before each launch

https://stackoverflow.com/questions/4507864/how-to-customize-the-title-bar-of-a-qt-app-through-qt-stylesheet Maybe you have to customize title bar. That means to create your own one.

@kkmspb Maybe you can see our free Qt project (4.8.1, Windows). This project contains several classes inherited from the base classes QSqlTableModel and QTableView. The PblSqlRelationalTableModel class is inherited from QSqlTableModel. The PblTableView class is inherited from QTableView. As a result, a combining class PblTableDlg was created with the composition PblTableView and PblSqlRelationalTableModel. The QTableView class contains full functionality for managing a database table: creating, copying, deleting rows. There is a search, selection by value. Fields in the form of combobox, checkbox,... External links and substitutions from other tabs work automatically. Everything is configured simply in one configuration file config.cpp . All three editing strategies are supported. [image: 4220_2.png]

@udx6bs said in QSqlRelationalTableModel questions: trying to experiment with QSqlRelationalTableModel and QTableView. I'm using the SQLite driver and Qt 4.8 compiled(32bit) on Win7/64bit. I have the following ques Maybe you can see our free Qt project (4.8.1, Windows). This project contains several classes inherited from the base classes QSqlTableModel and QTableView. The PblSqlRelationalTableModel class is inherited from QSqlTableModel. The PblTableView class is inherited from QTableView. As a result, a combining class PblTableDlg was created with the composition PblTableView and PblSqlRelationalTableModel. The QTableView class contains full functionality for managing a database table: creating, copying, deleting rows. There is a search, selection by value. Fields in the form of combobox, checkbox,... External links and substitutions from other tabs work automatically. Everything is configured simply in one configuration file config.cpp . All three editing strategies are supported. github

I don't see what this should have to do with qmake or cmake - those defines come from Qt (exactly: qsystemdetection.h, automatically included by qglobal.h) so make sure qglobal.h is included before you use those macros.

@Christian-Ehrlicher Thx. Issue closed.

@J-Hilk Thx that's what been seeking. Issue closed

@JeniaR said in QTimer understanding: That thread does some working and that's why it's required as a separate thread This still does not answer why a QTimer in this thread emits a signal which is handled in the main thread - this makes no sense.

@raven-worx said in QML update Image source with base64: Image { source: "image://mybase64/data:image/png;base64,iVBORw0KGgoA......" } No need for a custom QQuickImageProvider. QML can decode data URLs! Image { source: "data:image/png;base64,iVBORw0KGgoA......" }

@Christian-Ehrlicher As per Qt documentation Repaint , Repaints the widget directly by calling paintEvent() immediately, unless updates are disabled or the widget is hidden. As per my understanding, Repaint should invoke the paintEvent() immediately, but It observed similar behavior both update() and repaint().

Hi, welcome to te forum. Qt uses native file dialogs. It's an internal exception of the Windows API and it is handled there. You can safely ignore it and continue debugging.

@cristian-adam Thanks a lot. The argument is set in my CMakeSettings file and I didn't recognize that Visual Studio 17 2022 implicitly means Win32. I set it to Win64 and it works. Sorry for thinking that this doesn't work in general. I thought I already made a boiled down example, but obviously missed that one.