@manel-sam said in Serial data received: So the append I should do it where§? Create a member variable in your imu class. // _packetData member variable of imu _packetData.append(serialPort->readAll()); if(_packetData.size()>=PACKET_LENGTH) { // packet complete qInfo() << QStringLiteral("data size is : ") << _packetData.size() << " octets"; qDebug() << "Serial received " << _packetData.toHex(); // go ahead with this packet QDataStream stream(_packetData); // Read The BigIndian value stream.setByteOrder(QDataStream::BigEndian); qint16 headerSignature; stream >> headerSignature; } You may also check the data received don't exceed PACKET_LENGTH, cause it means you have already received data from the next packet. (it may be irrelevant in your case, I don't kown)

@raven-worx do you know of any project to "Qt-ize" the interface? Currently they use their own String class, which makes working with it difficult

Hi @Michael-R-LegakoL-3com-com, I think a better approach, is to use a macro to apply the dllimport/export, and then enable that macro in the library only. For example, if you look at qmake's simple_dll test example, the simple.h header contains: #ifdef SIMPLEDLL_MAKEDLL # define SIMPLEDLL_EXPORT Q_DECL_EXPORT #else # define SIMPLEDLL_EXPORT Q_DECL_IMPORT #endif class SIMPLEDLL_EXPORT Simple { ... } Then the simple_dll.pro file contains: DEFINES += SIMPLEDLL_MAKEDLL So, this way, when the library is being built (via simple_dll.pro), then class is dllexport'ed. But when other code uses that same header (in doesn't define SIMPLEDLL_MAKEDLL) then that same class is dllimport'ed instead. Typically, you end up doing this sort of thing to many classes in a single library, so rather than having the #ifdef ... #define ... etc in each header file, it often ends up being written once in a "global" project header of some kind. For example, Q_CORE_EXPORT gets defined in qglobal.h, then used throughout all of the exported core Qt class headers. Also see: When creating a library with Qt/Windows and using it in an application, then there is a link error regarding symbols which are in the library Cheers.

@Qjay You can get text like this, Create instance of search.qml means like Search(this is your search.qml file instance, first latter should be capital of your qml file) { id: searchText } 2 In search.qml file create property like property alias Name_of_variable(like textOfSearchField): id_of_textfield(search_text.text) Now wherever you want to use, can do like this. searchText(id_of_instance).Name_of_variable You will find exact value as you passed in search.qml file

Nice one ! I've missed that function. Thanks !

Sorry, my fault ... I will hold back this inner ironic imp in the future.

@LuGRU Why not to use: QSharedMemory and You don't need to worry about message formatting. Because I run process with different account. First process run from System account and second from local account When I read SharedMemory in another process I have error "QSharedMemory handle doesn't exist"

Yeah, according to QComboBox code should work: QVariant QComboBox::itemData(int index, int role) const { Q_D(const QComboBox); QModelIndex mi = d->model->index(index, d->modelColumn, d->root); return d->model->data(mi, role); } Will implement this.

@SGaist Yes, It worked me out.

@Adityan-J Yes. Use QDataStream and QFile. Here's one example.

@mcosta i am able to view the page inside the browser tho, why can't Qt read it then?

@XADOOO said: ast