General and Desktop

@Christian-Ehrlicher, it work well now as expected after i created my own dialog inherit QDialog and used setStyleSheet for the whole personal dialog. thank you for your help.

everybody please vote for this bug, thanks.

@SGaist I tried that but libqtlua still couldn't figured out to use uitools. I did got it to work by fixing the libqtlua.so library by adding /usr/local/src/qt5-build/qtbase/lib/libQt5UiTools.a to the generation of libqtlua.so via: /usr/bin/c++ -fPIC -shared -Wl,-soname,libqtlua.so -o libqtlua.so CMakeFiles/qtlua.dir/qtluaconsole.cc.o CMakeFiles/qtlua.dir/qtluaenum.cc.o CMakeFiles/qtlua.dir/qtluaenumiterator.cc.o CMakeFiles/qtlua.dir/qtluafunction.cc.o CMakeFiles/qtlua.dir/qtluauseritem.cc.o CMakeFiles/qtlua.dir/qtluauseritemmodel.cc.o CMakeFiles/qtlua.dir/qtluauseritemselectionmodel.cc.o CMakeFiles/qtlua.dir/qtluauserlistitem.cc.o CMakeFiles/qtlua.dir/qtlualistiterator.cc.o CMakeFiles/qtlua.dir/qtluamember.cc.o CMakeFiles/qtlua.dir/qtluametacache.cc.o CMakeFiles/qtlua.dir/qtluamethod.cc.o CMakeFiles/qtlua.dir/qtluaplugin.cc.o CMakeFiles/qtlua.dir/qtluaproperty.cc.o CMakeFiles/qtlua.dir/qtluaqmetaobjecttable.cc.o CMakeFiles/qtlua.dir/qtluaqmetavalue.cc.o CMakeFiles/qtlua.dir/qtluaqmetaobjectwrapper.cc.o CMakeFiles/qtlua.dir/qtlualuamodel.cc.o CMakeFiles/qtlua.dir/qtluaqobjectiterator.cc.o CMakeFiles/qtlua.dir/qtluaqobjectwrapper.cc.o CMakeFiles/qtlua.dir/qtluaqtlib.cc.o CMakeFiles/qtlua.dir/qtluastate.cc.o CMakeFiles/qtlua.dir/qtluaitemviewdialog.cc.o CMakeFiles/qtlua.dir/qtluatablegridmodel.cc.o CMakeFiles/qtlua.dir/qtluatableiterator.cc.o CMakeFiles/qtlua.dir/qtluatabletreekeys.cc.o CMakeFiles/qtlua.dir/qtluatabletreemodel.cc.o CMakeFiles/qtlua.dir/qtluauserdata.cc.o CMakeFiles/qtlua.dir/qtluavaluebase.cc.o CMakeFiles/qtlua.dir/qtluavalue.cc.o CMakeFiles/qtlua.dir/qtluavalueref.cc.o CMakeFiles/qtlua.dir/qtluadispatchproxy.cc.o CMakeFiles/qtlua.dir/QtLua/moc_qtluaconsole.cpp.o CMakeFiles/qtlua.dir/QtLua/moc_qtluauseritemselectionmodel.cpp.o CMakeFiles/qtlua.dir/QtLua/moc_qtluauseritemmodel.cpp.o CMakeFiles/qtlua.dir/QtLua/moc_qtlualuamodel.cpp.o CMakeFiles/qtlua.dir/QtLua/moc_qtluatabletreemodel.cpp.o CMakeFiles/qtlua.dir/QtLua/moc_qtluaitemviewdialog.cpp.o CMakeFiles/qtlua.dir/QtLua/moc_qtluatablegridmodel.cpp.o CMakeFiles/qtlua.dir/QtLua/moc_qtluastate.cpp.o CMakeFiles/qtlua.dir/moc_qtluaqtlib.cpp.o /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.12.8 /usr/local/src/qt5-build/qtbase/lib/libQt5UiTools.a /usr/local/lib/liblua.a -lm -ldl /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.12.8 /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.12.8 /usr/bin/c++ -fPIC -shared -Wl,-soname,libqtlua.so -o libqtlua.so CMakeFiles/qtlua.dir/qtluaconsole.cc.o CMakeFiles/qtlua.dir/qtluaenum.cc.o CMakeFiles/qtlua.dir/qtluaenumiterator.cc.o CMakeFiles/qtlua.dir/qtluafunction.cc.o CMakeFiles/qtlua.dir/qtluauseritem.cc.o CMakeFiles/qtlua.dir/qtluauseritemmodel.cc.o CMakeFiles/qtlua.dir/qtluauseritemselectionmodel.cc.o CMakeFiles/qtlua.dir/qtluauserlistitem.cc.o CMakeFiles/qtlua.dir/qtlualistiterator.cc.o CMakeFiles/qtlua.dir/qtluamember.cc.o CMakeFiles/qtlua.dir/qtluametacache.cc.o CMakeFiles/qtlua.dir/qtluamethod.cc.o CMakeFiles/qtlua.dir/qtluaplugin.cc.o CMakeFiles/qtlua.dir/qtluaproperty.cc.o CMakeFiles/qtlua.dir/qtluaqmetaobjecttable.cc.o CMakeFiles/qtlua.dir/qtluaqmetavalue.cc.o CMakeFiles/qtlua.dir/qtluaqmetaobjectwrapper.cc.o CMakeFiles/qtlua.dir/qtlualuamodel.cc.o CMakeFiles/qtlua.dir/qtluaqobjectiterator.cc.o CMakeFiles/qtlua.dir/qtluaqobjectwrapper.cc.o CMakeFiles/qtlua.dir/qtluaqtlib.cc.o CMakeFiles/qtlua.dir/qtluastate.cc.o CMakeFiles/qtlua.dir/qtluaitemviewdialog.cc.o CMakeFiles/qtlua.dir/qtluatablegridmodel.cc.o CMakeFiles/qtlua.dir/qtluatableiterator.cc.o CMakeFiles/qtlua.dir/qtluatabletreekeys.cc.o CMakeFiles/qtlua.dir/qtluatabletreemodel.cc.o CMakeFiles/qtlua.dir/qtluauserdata.cc.o CMakeFiles/qtlua.dir/qtluavaluebase.cc.o CMakeFiles/qtlua.dir/qtluavalue.cc.o CMakeFiles/qtlua.dir/qtluavalueref.cc.o CMakeFiles/qtlua.dir/qtluadispatchproxy.cc.o CMakeFiles/qtlua.dir/QtLua/moc_qtluaconsole.cpp.o CMakeFiles/qtlua.dir/QtLua/moc_qtluauseritemselectionmodel.cpp.o CMakeFiles/qtlua.dir/QtLua/moc_qtluauseritemmodel.cpp.o CMakeFiles/qtlua.dir/QtLua/moc_qtlualuamodel.cpp.o CMakeFiles/qtlua.dir/QtLua/moc_qtluatabletreemodel.cpp.o CMakeFiles/qtlua.dir/QtLua/moc_qtluaitemviewdialog.cpp.o CMakeFiles/qtlua.dir/QtLua/moc_qtluatablegridmodel.cpp.o CMakeFiles/qtlua.dir/QtLua/moc_qtluastate.cpp.o CMakeFiles/qtlua.dir/moc_qtluaqtlib.cpp.o /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.12.8 /usr/local/src/qt5-build/qtbase/lib/libQt5UiTools.a /usr/local/lib/liblua.a -lm -ldl /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.12.8 /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.12.8 then type "make" and that's it. Once libqtlua.so has the Qt5UiTools symbols through the .a, then the problem is fixed. Wish it just worked out of the box though. Thanks.

@artwaw Thanks a lot ! It works. I don't know how I could miss this one. It seems that every time I restart the server, the IP changes. I will have to set a fixed IP adress.

Hello all, Sorry for the long delay in response, I had other issues in this project to work on. The solution to this issue was found, I was using my own extension for the files and it was making windows antivirus grab the files and scan them. Changing the extension to a simple .txt circumvented this issue. Thanks all for your help on this.

Documentation clearly states: Note: It is not supported to let the effect include itself, for instance by setting source to the effect's parent. So you can't set the blur to fill parent object.

@Px_Forever said in "Unimplemented code", What`s this?: SO, this mean whether Qt hadn`t implement this function on windows platform. Yes

@crow said in Type Erasure In QModelIndex: @jeremy_k said in Type Erasure In QModelIndex: alluded I don't know what quoting this word on its own means. so this "Abstract" model just for static model. Image that you have a dynamic tree with thousands of items. As time goes by, thousands of items add to tree, and thousands of items remove. This doesn't describe anything that QAbstractItemModel can't be used for. The efficiency of the underlying data structure and access patterns will have an impact on performance, but this is true for data structures in general. and the model hold item warp index object which have been romove from tree and never use again because model lifetime is at the end. the memory usage must be crazy. Why is storing the type for a mixed data tree's node in the tree more expensive that storing them separately? If that data is only stored in a temporary index, how is that index constructed in the first place?

@SGaist The name we give to Internet communications. For example, my wireless connections name. [image: f33ab598-b0e5-4095-b1a1-3934ac605359.PNG]

Thank you, @SGaist ! You're completely right. The code inside the Worker's slot would then execute in a separate thread. However, you are free to connect the Worker's slots to any signal, from any object, in any thread. It is > safe to connect signals and slots across different threads, thanks to a mechanism called queued connections. https://doc.qt.io/qt-5/qthread.html

Hi and welcome to devnet, Why action widgets ?

progressBar->setInvertedAppearance(true);

@aftalib can you poste the code + show me how you've organised your layouts please?

@SGaist Thanks. =) That basically worked this way: QOAuth2AuthorizationCodeFlow *oaFlow; // ... *oaFlow gets authorized ... QNetworkRequest nrqRequest(QUrl("https://somesite.com/someres/somecmd?someparam")); // I don't know what the verb/body parameters are good for: oaFlow->prepareRequest(&nrqRequest,QByteArray(),QByteArray()); nrqRequest.setRawHeader("X-SOMETHING","blah"); QNetworkReply *nrpReply=oaFlow->networkAccessManager()->get(nrqRequest); I don't like having to create a QNetworkRequest myself, but for a one-time use, it's fine. Also, at this point I already had created a custom QNetworkAccessManager re-implementing createRequest() and including some methods to add/remove raw headers. And then used QAbstractOAuth::setNetworkAccessManager() to link it to the authorized object.

If I am not mistaken the relation between the physical and logical pixels is the scaling factor (usually set by the operating system). For example, Apple's Retina displays usually have a scaling of 200%. Which means that for every logical pixel there are 2 physical pixels (actually 2 in x- and y-direction each; which makes 4 in total) inside your display. You should try to change the scaling in your OS and then write a small toy program to see what physical and logical DPI you get. The physical DPI should be fixed.