Why my object stay in main thread?

[Santosh Reddy]

I puzzled with 4 and 5. I have used moveToThread function to move the m_spDevPort to the monitor thread, but its member m_spSerialPort still stayed in the main thread.

your problem is that m_spSerialPort's parent is not set.

CSerialPort::CSerialPort()
{
	// Create serial port object
	m_spSerialPort = new QSerialPort(this); //<<<<<<<<<<<<<<<< Pass the parent while object creation.
        // 1. print the thead where m_spSerialPort lived in
	printThreadID(); 
 
	// Timer for send command
	m_tQueryTimer = new QTimer;
 
}

CSerialPort::CSerialPort()
{
	// Create serial port object
	m_spSerialPort = new QSerialPort(this); //<<<<<<<<<<<<<<<< Pass the parent while object creation.
        // 1. print the thead where m_spSerialPort lived in
	printThreadID(); 

	// Timer for send command
	m_tQueryTimer = new QTimer;

}

To copy to clipboard, switch view to plain text mode 

[kuzulis]

I wanted to create a serial port monitor thread. I used QT4.8.6 + QSerialPort(latest) on Windows XP.

Using the QSerialPort library is not good idea.

Is better to use - QtSerialPort library.

[ChrisW67]

Using threads is probably unnecessary also.

[honestapple]

Yes, it is QtSerialPort library.

---

Added after 26 minutes:

Yes, I knew that you have mention that. I am doing a USB DAQ GUI part on PC using QT4.8.6+QWT6.0.2 under Windows XP. I should receive data from device and display waveform, frequency spectrum, etc. I have made a demo without threads which could receive and send command( using timer ) at a interval, but I could not display the wavefrom in realtime. In fact, it was not that the waveform could not be displayed completly. It is sometimes good, sometimes bad. When it was bad, I knew that there are something wrong with the QwtCPointerData. Because there are many operation in main GUI thread, I wanted to tried to use monitor thread to release GUI thread from doing data receiving and sending command.