General and Desktop

At this point, no. Part of it appears to be interaction between multiple apps and a custom Window Manager (all Qt based). The next thing we are thinking of trying is downloaded the latest Qt5.15 source, and adding debug to track outgoing/incoming XCB events/activities relating to sizeing, mapping and exposing and see if that gives us a clue to what is going on. Dale

If you are looking for the best custom software development company you can mail us at business@binmile.com.We will provide end to end quality in building the best software for you. Some of our well known clients are Adani, Indigo airlines and Reliance Industries.

@lartimus could you find any solution for this situation. I have same warnings for d3d11 also. I can't find any solution for this.

@Pariposh You would need to build Qt and ALL dependencies as static libraries. Also, if you do static linking with LGPL software you have to consider the obligations of that license! Basically it would mean to provide the source code of your application to everyone who has access to your application and asks you for source code.

@SGaist I found a possibile solution using QScrollArea.. I needed to add a VerticalLayout into ScrollAreaContentWidget and then add the compound widget to such layout: void MainWindow::addTestItem(QString name, QString description, QVBoxLayout *layout) { QTest *_test = new QTest(name, description); TestWidget *_widget = new TestWidget(_test); layout->addWidget(_widget); } Now it seems to display correctly: [image: 3f5e8b53-05b8-4de1-bf4c-4eb363b6a654.png]

@g-suresh said in Signal Slot Communication Time Over Queued Connection: Can you please point me link or material on how to invoke methods directly across threads in QT without using signal slot/Event loop at all. Nothing Qt specific here: simply call a method of the other class living in another thread. But then you need to consider two things: You have to do synchronisation if needed You are not allowed to manipulate the UI from other threads, only from main/GUI thread "so I assume the event loop immediately picks the next signal" - it picks the next signal next time the event loop is activated. When the event loop is activated and how often I don't know.

@masa4 :) Use my update to last post while you get it right, then change to bound values.

@mpergand Hey I tried it and it works perfect with 3 layouts.Now middle labels always at center.

@Krpadia123 said in setMinimumWidth and setMaximumWidth not working: textLabel->setMinimumWidth(100); // Not working textLabel->setMaximumWidth(400); // Not Working This sets min/max width for the label, it has nothing to do with the tool tip. I don't think there is a way to define max/min width for tool tips as those are just strings. You can try to insert new line ('\n') in your string when it is is too long to force a line break.

How are you doing things differently from the example ?

Hi, You can throw a QTabBar in the mix for the switch between your widget or depending on your needs a QTabWidget. I don't think there's any status bar there. Rather a small custom one line widget.

It's not related to Qt or windeployqt and it's not about how the exe is made. Windows has a defined search order when it loads linked dynamic libraries. Other dlls, like plugins or resources, that load later on demand can be relocated via qtconf file. In short - that's just how Windows organizes dlls. You can fiddle with the local startup environment e.g. make a batch script that adds the dependencies subdirectory to PATH or changes working dir and you'd start your app by running it, but it's quite unusual and ugly. I'd say just get used to having bunch of dlls next to your exe, even if it's not to your taste. That's what Windows apps do.

It's not a property. If you look at the generated code it's just a shortcut for setting the variable and object name i.e. something like this: page = new QWidget(); page->setObjectName("page"); stackedWidget->addWidget(page); so to get it back you would do: ui->stackedWidget->currentWidget()->objectName()

@Pekoyo Thanks for all the answers: here is my solution if it helps anyone in my class WidgetStyle simply add struct WidgetStyle: QWidget { Q_OBJECT public: WidgetStyle(); }; qobject_cast<WidgetStyle* >(MYLayout->itemAt(i)->widget())->MY_Style

@Sociostar Any reason you're replied to me more or less repeating what I wrote?

@SOrton Not (so far as I know) in a Qt library. Use the std:: library for this sort of functionality (or write it yourself).

@agmar It would be better if you pasted some minimal example of your problematic code. But if you are going to post code as big as this please use the forum's Code tags around code blocks. Meanwhile, your MainWindow::sendMessage() at least has a local QSerialPort and opens and closes it. I don't know about the rest of your code, but you are supposed to have a single instance of QSerialPort permanently open for both writes & reads.