General and Desktop

I had very good help from the Qt staff, although I found the solution to be verbose but that would serve for the time being https://bugreports.qt.io/browse/QTBUG-95321?focusedCommentId=576678&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-576678

Are these REST services ?

@Pl45m4 oops,It works well,thanks.Here is result [image: 03be47bc-ee3d-471f-b8a0-2fa5d1c72937.png]

Hi, I'm trying to do something similar: a month/week/day view widget to use instead of the calendar. If you had any wish to share your code it would be greatly appreciated :) Thanks, Jerome

My bad I had set 077 umask (cause I'm paranoid) and had no read permission set on /etc/fonts/local.conf which had fallback configuration. I gave read permission to all and reran fc-cache and now everything is working fine.

@Qt-embedded-developer try delete the build folder from file explorer and rebuild all

@AnneRanch Only another note When you manually connect a control's signal to your slot don't use the same name of "go to slot" because else your slot will be called twice, once for "go to slot" mechanism and once for your connect. e.g. if you have a push button called on_pushButton_13 you musn't call your slot void on_pushButton_13_clicked(bool checked); if you use the connect function to manage clicked signal. I hope I'm clear, no for you but for my english :(

@raven-worx Thank you very much! I must have missed this piece of documentation.

@Pl45m4 I want to close this out for future devs looking for the right answer. The above solution is run before dockwidget->hide() and deleteLater(). We aren't ever undocking the dockwidget here. As far as I understand, my solution sends an event to the QMainWindow telling it the left mouse button was released, and the mainwindow responds accordingly, in this case, it ends the resizing of the dockwidget. The reason we send the event to the qmainwindow is that it is in charge of the dockwidget separators; I figured this out from some inspection of the source code and searching online. Also notably, the pointer to our parent qmainwindow is guaranteed safe in my implementation. The code that closes the dockwidget is running in the scope of the qmainwindow and we are just using 'this'. It might be dangerous to use this code within the scope of the qdockwidget and get the pointer to the parent with parent().

@ChrisW67 ok i copied that exactly, and it actually changed the output of the error code. So I think it actually worked. There were some other errors involving cmake. But I contacted the devs of the kdeconnect app and they suggest I use something called craft to build the application and test changes to code. I'm gonna leave that last post as the solved answer, because it did work.

You can also try to align G label to left when it is added to the layout. something like: layout->addWidget( g_label, 0 , Qt::AlignLeft ); In this case, spacer may not be needed at all.

@Garza said in Qpixman makes gui run slow: @SGaist currently I'm just calling this function and not handling what you mentioned. Will have a look at it. Does image size is an issue? is 2048x1280. It depends on: At which pace do you load them ? file compression level storage type and speed if network, network speed your machine specification

@BDC_Patrick You can launch your app(GUI) quickly while throwing loading of files into a thread.

void QAbstractItemView::setCurrentIndex(const QModelIndex &index) does this help?

Hi I think its something with the QtOpcUa plugin as when I tried using open62541 API directly it worked but I was not able to get working using the Qt API. But I didn't find out why exactly and for my use case, using the native API was ok. If you dont get any answers here I would ask on the mailing list. https://lists.qt-project.org/

In my main routine I added to following 2 lines int main(int argc, char *argv[]) { // Set up High DPI Scaling QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling,true); std::cout << "Enable High DPI Scaling to " << (QCoreApplication::testAttribute(Qt::AA_EnableHighDpiScaling) ? "true" : "false") << std::endl; // Existing Code QApplication a(argc,argv); // rest of main } I still saw the same font scaling and clipping issue. As a possible alternative, I tried swapping out the AA_EnableHighDpiScaling with AA_Use96Dpi, but that did not change anything. Dale

@mrjj That is unfortunate .... anyway thank you for the help ! I will investigate this library. I already tried something similar in Python without success. Hoping this one will work. For now I keep this topic open just in case someone find a solution to this issue.