StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19375466
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-10-15T07:26:12.240
FavoriteCount
0
LastActivityDate
2013-10-15T17:17:08.437
LastEditDate
2013-10-15T17:17:08.437
LastEditorUserId
2804358
OwnerUserId
2804358
ParentId
19375141
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You've fallen into the same trap as many do when working with threads in Qt: <a href="http://blog.qt.digia.com/blog/2010/06/17/youre-doing-it-wrong/" rel="nofollow">http://blog.qt.digia.com/blog/2010/06/17/youre-doing-it-wrong/</a>. It is almost always a bad idea to subclass QThread (see <a href="http://woboq.com/blog/qthread-you-were-not-doing-so-wrong.html" rel="nofollow">http://woboq.com/blog/qthread-you-were-not-doing-so-wrong.html</a> for counterexamples). Change your code as follows to do it the "intended" way (create a new QThread and call moveToThread on your QObject to move it to the new thread). You'll see from the output that the thread the UdpReceiver is created on is not the same as the one it receives data on, which is what you want: <pre><code>#include <QApplication> #include <QDebug> #include <QThread> #include <QUdpSocket> class UdpReceiver : public QObject { Q_OBJECT private: QUdpSocket * S; int port; public: UdpReceiver(QObject* parent = 0) : QObject(parent) { qDebug() << "Construction thread:" << QThread::currentThreadId(); port = 9003; initialize(); } UdpReceiver(int p,QObject* parent = 0) : QObject(parent) { port = p; initialize(); } void initialize() { S = new QUdpSocket(); S->bind(port); S->connect(S,SIGNAL(readyRead()),this,SLOT(readPendingDiagrams())); qDebug() << "Waiting for UDP data from port " << port << " ... \n"; } public slots: void readPendingDiagrams() { qDebug() << "Reading thread:" << QThread::currentThreadId(); while(S->waitForReadyRead()) { QByteArray datagram; datagram.resize(S->pendingDatagramSize()); QHostAddress sender; quint16 senderPort; S->readDatagram(datagram.data(), datagram.size(),&sender, &senderPort); qDebug() << datagram.size() << " bytes received .... \n"; qDebug() << " bytes received .... \n"; } } }; int main(int argc, char *argv[]) { QApplication a(argc, argv); QThread *t = new QThread(); t->start(); UdpReceiver * net = new UdpReceiver(); net->moveToThread(t); return a.exec(); } #include "main.moc" </code></pre> I don't have your UI code, so I don't know about any issues there. Feel free to post another question if you get stuck there and mention it in a comment and I'll try to help.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POudp packet is not received in QThread
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USksimons
UserOwnerUserId
1. USksimons
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POudp packet is not received in QThread
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COGreat Answer, Thank You! however when I use what you suggested I get this message in console several times : "QSocketNotifier: socket notifiers cannot be disabled from another thread " Is it something I should worry about (disabling sockets from another thread)? How can I fix this?
 singulars
 PostPostId
 PO
 UserUserId
 USVahid Nateghi
2. COSorry, I've never actually seen that message. Maybe you should post a new question. If I have some time later I could take a look.
 singulars
 PostPostId
 PO
 UserUserId
 USksimons

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.