That did the trick, thank you very much! I would have never found the problem.
One more question out of curiosity: isn't it quite ineffient, if clients continuously invoke vtkNetworkAccessManager::ProcessEvents´()? For smooth interaction this has to happen at least 10 times per second, which causes a lot of network traffic by polling the server again and again, especially if more than one client connects to the same server. Isn't it possible to react on incoming server events by registering a callback that does the same server event processing only when a new event has occurred? I mean, all of VTK and ParaView is event based, why not the server message processing? Peter 2016-06-09 18:29 GMT+02:00 Utkarsh Ayachit <[email protected]>: > Here's the fix: > > diff --git a/main.cxx b/main.cxx > index dd47991..0f679ba 100644 > --- a/main.cxx > +++ b/main.cxx > @@ -65,7 +65,7 @@ int main(int argc, char* argv[]){ > vtkSMSessionProxyManager* pxm = session->GetSessionProxyManager(); > > //Collaboration: > - vtkSMCollaborationManager > *collaboration=vtkSMCollaborationManager::New(); > + vtkSMCollaborationManager *collaboration= > session->GetCollaborationManager(); > collaboration->SetSession(session); > collaboration->UpdateUserInformations(); >
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
