General and Desktop

... Or if two distinct functions should be called where none is aware of the other?

It looks like it's statically building. When I go into the directory, inside the bin folder there is no dlls, when I do the lib /list some.lib, it shows how .obj files instead of .dll files. Weirdly enough, when I statically compile with the dynamic dll version of QT, it compiles fine, although it still requires the dlls.

That is the way to go. Also don't use a QSqlDatabase object as member. Always reference it through the static functions and it's name.

@JonB after reconsideration it might have worked when the const ref was copied to a new QSqlQuery instance This copy was removed in Qt6 as it's impossible to copy a query without getting strange side effects in the underlying layer.

@Jammin44fm said in QMetaMethod::tag() problem: It lists 6.0.0 as an affected version, but nothing more recent Then its not yet fixed. If there is no minimal reproducer you can add one.

@Radio1985 ui file. uic is the user interface compiler.

@SGaist Ok, here is the thread link: https://lists.qt-project.org/pipermail/development/2023-August/044234.html

@SGaist Qt version: 5.15 os is Windows Server 2022 Datacenter Evaluation version is 21H2

@Christian-Ehrlicher This is the file referred to by the OP. The PRI file is used when building the examples only; the main library uses CMake. The comment that the OP omitted reads: # Note: Due to Angle, windows might use either OpenGL (desktop) or # OpenGL ES (angle) backend. Newer Qt versions don't automatically # link with OpenGL ES libraries. win32 { equals(QT_MAJOR_VERSION, 5):lessThan(QT_MINOR_VERSION, 14) { ... This might provide a reason for explicitly linking the library. Like you I imagine this needs to be provided separately. It also strikes me that the comment and the PRO file logic are opposite in regard to the Qt versions i.e., it explicitly links for older version not newer versions.

@KenAppleby-0 I think I found, the main thing was to turn off these calls buried in the code recesses setAutoFillBackground( true ) And the management of the palette and the background image needs to be reviewed. But even if other things malfunction now, partial transparency works. I've made some changes, the graphic effect is better and the code is substantially definitive (if it can be useful to someone else). void Panel::paintEvent( QPaintEvent *e ) { Q_UNUSED(e); QPainter p( this ); QRect qrRect; QColor qcRectColor; qrRect = rect(); qrRect.adjust( 1, 1, -1, -1 ); qcRectColor = palette().color( QPalette::Background ); qcRectColor.setAlphaF( 0.7 ); // p.setRenderHint ( QPainter::Antialiasing ); p.setPen( palette().color( QPalette::Background ) ); p.setBrush( qcRectColor ); p.drawRoundedRect( qrRect, 45.0, 45.0); QFrame::paintEvent( e ); } [image: b7b1affb-546b-4f57-8eb2-5b6a45f68195.png]

Hi and welcome to devnet, That's a pretty intriguing question. I think you should bring it to the interest mailing list. You'll find there Qt's developers/maintainers. This forum is more user oriented.

@SGaist it works thanks a lot Miłosz

@wrosecrans #include "qcustomplot.h" // Инициализируем объект полотна для графика wGraphic = new QCustomPlot(); ui->gridLayout->addWidget(wGraphic,2,0,5,5); // и устанавливаем // Добавляем график на полотно wGraphic->addGraph(wGraphic->xAxis, wGraphic->yAxis); // Подписываем оси координат wGraphic->xAxis->setLabel("итерации"); wGraphic->yAxis->setLabel("Дб"); // Устанавливаем максимальные и минимальные значения координат wGraphic->xAxis->setRange(0,100); wGraphic->yAxis->setRange(-50,50); // Отрисовываем содержимое полотна wGraphic->replot(); // добавляем красную линию на график wGraphic->addGraph(); // red line wGraphic->graph(0)->setPen(QPen(QColor(255, 110, 40))); // чистим старое отрисовываем новое wGraphic->graph(0)->clear(); wGraphic->graph(0)->rescaleAxes(); wGraphic->graph(0)->setData(y,x); // Устанавливаем координаты точек графика wGraphic->replot(); // Отрисовываем содержимое полотна

@Vijaykarthikeyan Please now get help from other people than me. I'm done.

@Axel-Spoerl Thanks for the suggestion. pushButton->setStyleSheet("text-align:left;"); does fix the issue. Yes it does make sense to name it as menuButton. Initially I had a button for the menu icon and then a label separately. So I was using menuIcon for the button name which I should have changed in the new design. I thought of having application related button options on the GUI main window it self rather than on the menu bar. By collapsing the menu bar to the left, I wanted to get more space from the main dash board side. Hope this makes sense. May be I should remove the wording "Menu" to avoid confusion.