General and Desktop

Hi, You can see the logic here. From the looks of it, you are right.

@xeroe Hi Ok that is also possible QJsonObject json { {"type", "textMessage"}, {"subobject", Obj} };

I forgot to mention - this layout is installed in the QWidget, i.e. splitter separates two widgets (QWidget, that contains vertical layout, that contains QLabel and QTreeView and QStackWidget). I figured out my mistake - I was setting the maximum width (setMaximumWidth) for the QTreeView object, not for the widget added to the splitter (QWidget). @Bonnie thank you!

@Pl45m4 Hehe well its fair to say VRonin is not thrilled about setIndexWidget in general but its mostly due to being very heavy and not the right way. But this issues does not happen with QListWidget (even if scrolling ) so I assume its due to how ComboBox works with its viewport.

Hi Just a note about docs Warning https://doc.qt.io/qt-5/qobject.html#sender "Warning: This function violates the object-oriented principle of modularity. However, getting access to the sender might be useful when many signals are connected to a single slot." While it does negatively affect the "loosely coupled" quality of the code, it's more along the line do not use this all over the place and cast sender() to all types of concrete widgets as it will be hard to reuse.

@SPlatten FTR: A TCP/IP connection is a unique combination of four numbers: server IP + port + client IP + port. the same combination cannot be reused. Usually the client specifies the server port to connect on but not which port to use from client side. That gets filled in during the connection (e.g. connectToHost()) with a "random", unused port number at client side. That's how the same client can make multiple, separate connections to the same server service port. You can see this by looking at the port numbers used at client side during, say, multiple FTP connections.

@mariozio said in /etc/profile.d/qt5.sh: line 2: pathappend: command not found : As a result the session will not be configured correctly,you should fix this problem as soon as feasible.: the error is gone. And kde still works If your issue is solved, please mark this post as such! Thanks.

Hi, One thing I can see is the missing opening of the database connection. You create one database, you assign it some path but I did not see any code opening the connection.

this worked for me: format.setScanLineDirection(QVideoSurfaceFormat::BottomToTop);

Ok, so shouldn't be required is my takeaway from this discussion. I'll probably leave the system("sync") for now just to be conservative.

@Helg1980 Nice to hear! Don't forget to mark your issue as solved.

@bam80 said in Using a const QString & if a function returns a QString: there is no copying occurs anywhere in the original code it is: const QString text = jsonObject.value(someKey).toString(); At least with c++11 or c++14. See https://en.cppreference.com/w/cpp/language/copy_elision

@Bonnie said in QFontDialog: How to set it size?: Somehow you asked about QFontDialog, but you are using QFileDialog in the code... Oh, sorry that was a typo. Thank you for the link to the documentation, I will read this part carefully.

@Pl45m4 I didn't know about QScreen and I thought that the only way to use my device screen geometry is using QDesktopWidget. I will change it to QScreen . About layouts, also I didn't know that I can set size for them :) Thank you for valuable points you mentioned. I will definitely use them in my project.

Thanks @JKSH

Yes you're right, I suppose I was just considering instances where the value is greater than 16 bits, in which case some additional manual processing would be required.

Using <div> elements to separate the lines instead of <br> solved the problem. setText( "<div><center>1 (2) </center></div><div><font color=#000000>09:12 : <b>titre Normal</b></font></div><div><font color=#FF1144>12:10 : <b>titre Rouge</b></font></div>" );

It's QPointer<QNetworkReply> so ::data() returns a pointer. Forgot to mention that. Also, I made it work by setting user and password in QUrl, not by setting QAuthenticator in response to QNetworkAccessManager::authenticationRequired. So... I don't understand why it didn't work before but now it works.

Then use the unpolish/polish QStyle trick.