[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [certi-dev] CERTI 3.4.1 conflict with Qt application?
From: |
Eric Noulard |
Subject: |
Re: [certi-dev] CERTI 3.4.1 conflict with Qt application? |
Date: |
Wed, 13 Nov 2013 07:50:26 +0100 |
2013/11/11 YangJing <address@hidden>:
> Hi,Bob:
> I am the Chinese CERTI user,posted to you several days ago.In that
> mail I said that I got debug message about 'libRTI:Network Read Error waiting
> RTI reply' while constructing RTIambassador object In my Qt application.
I'm not "Bob" but Eric, :-]
I'm sorry I have not much time right now to investigate your issue.
Nevertheless your are not subscribed to the certi-devel ML (or at
least not with the current posting address)
so that:
1) your mail are blocked in moderation
2) you won't get the answer from the list
please subscribe to the list:
https://lists.nongnu.org/mailman/listinfo/certi-devel
> Today I created two test projects in order to figuring out what is the
> real reason why CERTI library would fail in Qt application.And I found
> something.
> My A test project is a simple console app,B test project is a simple Qt
> app.They use the same set of files(the files's main aim is to create local
> federation ambassador ,join the RTI ,and publish some object types or
> subscribe some object message)which using CERTI library.Now A app can run
> correctly but B app fail sometimes.
> If I use a static RTIambassador object,I can get debug message'Error
> while receiving UN message'.SocketUN line 362. If I use dynamic
> RTIambassador object,I can get two different debug messages,one is
> 'libRTI:Network Read Error waiting RTI reply',the other is 'Cannot connect to
> RTIA'.
> Could you help me to tell me what is the fucking wrong whit my
> application?
It is really difficult to say without having a sample project to play with.
May be you can post a minimalistic project which shows the error?
I may be able to try it on Linux.
May be the problem comes from the fact that RTIambassador forks a RTIA
process then wait for some time
and then tries to connect to RTIA which should be listening to its
federate connection.
May be from within a Qt application the "wait" timing is wrong.
This is just a wild guess though.
May be other CERTI users can react about their experience of mixing Qt
with CERTI.
--
Erk
L'élection n'est pas la démocratie -- http://www.le-message.org