-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Send Open IGT Link after a message was recieved #177
Comments
Hello, Is there a question or problem? |
i don't know how to do that, the program needs to ckeck if a certain message was sent and afterwards send an Open IGT Link update |
Well, if your program is using sockets, then you'll have to check the return code from your send() function. Most of them will return an error code of timeout if the send did not complete. Are you using igtl::ClientSocket as your client connection? How do you want to send an update? Do you want to send an OpenIGTLink STATUS message? |
Yes i'm using iglt::ClientSocket and yes i want to send an OpenIGTLink Status.
For now i'm doing it in a endlessloop. But i want it to directly react to the sent message.
So if there is a new message i want it to send an Open IGTLink Status.
|
Do you mean receiving a message? Or do you want to react to your own sending of messages? igtl::Socket::Send(...) (parent of ClientSocket) wraps send(...) If it returns with no error code, the data has been sent successfully. |
I have connected NDI Polaris Vega ST to PlusServer, and 3D Slicer. I want to send the transforms information and the position data to python, have you tried to do this? @adamrankin |
Hello, I want to connect NDI Polaris Vega ST to PlusServer and 3D Slicer, but now I keep getting errors when connecting NDI Polaris Vega ST to PlusServer. I have read various forums, but the problem keeps occurring: |
@ningw-git The issue seems to be related to PlusServer, not OpenIGTLink. Can you post your question to https://github.com/PlusToolkit/PlusLib/issues ? |
No description provided.
The text was updated successfully, but these errors were encountered: