General and Desktop

@Alex_wang You should have much more output when starting with QT_DEBUG_PLUGINS set.

Or just do the right thing and use a delegate (QStyledItemDelegate subclass) for the columns instead of setCellWidget

@Jonathan-Levanon Hi Normally you create a deployment folder containing a few subfolders ( like platforms ) and the needed dlls/so files. http://www.tripleboot.org/?p=138 http://doc.qt.io/qt-5/linux-deployment.html You can also test this app https://github.com/probonopd/linuxdeployqt (i have not tried it yet) To inform the loader on linux about the so files in the folder, you can use rpath.

@sunghwawe Hi and welcome to devnet forum I guess your other post is about the same topic. According to google translate this is Korean. All posts in non-language specific fora shall be in English. Unfortunately, we do not have a Korean forum, yet.

@Decroit Did you install QGroundControl? It is not part of Qt.

@hskoglund said in The most bizarre bug I have ever seen, Random Chinese translation? How can this happen?: Hi, do you delete the ""communication_log.txt" file every time before running your app? Otherwise it could be some junk characters lingering at start of the file that causes your Chinese woes... Yes I do. The log's purpose is to locate bugs so I have no need to keep track of previous logs. @artwaw said in The most bizarre bug I have ever seen, Random Chinese translation? How can this happen?: Hi, have you tried: log.open(QIODevice::Text | QIODevice::Append);? No I have not. I think I will add it. I already changed some code and it does not happen anymore, but I'll add it anyway ;)

@Vinod-Kuntoji I think the problem happends when Qt program sends the data to MySQL. I have no problem with typical english characters but with acents and Ñs is another story.

@VRonin Thank you. This worked with the following changes: QGridLayout* mainLay = new QGridLayout(this);

@samdol I hope you get same result :) You can download sp 1 as a file and move to other machine.

I guess if there had been concern of a leak, that was apparently a false positive of a unit test. (I'm not sure about this detail). This has been resolved, as of today. Here is a summary: This bug originally appeared in Qt 5.0, was reported in Qt 5.3.0 (QTBUG-39147), and fixed for Qt 5.9.2 (on 7-19-2017). The removal of Qt_WS_* macros (replaced with Q_OS_* macros), and incomplete porting of the widgets/kerna/qtooltip.cpp module, caused the QTipLabel to be instantiated with the client widget as its parent widget. That had been a known problem on Windows which directly caused this dysfunction (Showing a tooltip raises the whole window). See "Patch Set 6" in this Qt code review page, and it's associated "gitweb" link, and the original bug report: https://codereview.qt-project.org/#/c/177376/ https://bugreports.qt.io/browse/QTBUG-39147

The output of qDebug will partly depend on your locale as well as it will escape non-printable characters.

@sontung If it is a windows application, without layout, the content widget won't expand or shrink automatically when you resize you window. For example, Text edit widget inside dialogBox will not expand or shrink as resizing dialog box which is not convenient for users.

@Phill said in Stuck trying to understand model/view in Python: But does not allude to a way for the data structure to let the model know that it has changed. For example if "Device 1" communicates that recording has stopped how would I inform the model that the recording attribute has changed? That is because it's entirely up to you. The model is just a interface (a facade) for the data. You must ensure that it emits the appropriate signals so it notifies the view, and if your model's data can be edited from the view, then it must also implement QAbstractItemModel::setData and friends, but there are no real requirements on how the model will bookkeep the dataset (if at all). One possibility is that your device is represented by a QObject and emits signals which are connected to slots in your model.

The easyest way is using QDockWidget or QMdiSubWindow (but the first is probably what you want)

@mzimmers said in C++ <complex> yielding strange behavior: I'd expect the .exe suffix to prevent it, but who knows... Yes, that is correct, it's a linux/mac peculiarity.

Thanks you all. It works now. I configured it using gitbash of MinGW Distro and now i can use qttelnet in my poject including the .pri as mrjj said !.