Thanks for the reply, but vtkNetworkAccessManager::ProcessEvents() is already called in the attached example every 100ms repeatedly until it returns false. See my code at Callback::Execute(). The Timer Callback is started towards the end of main.cxx, where it says "Callback *timer=Callback::New();" and the following lines.
If you run the example as described, you'll see that actually a number of messages are processed (their number is being logged). But I don't know how I can print the content of the received vtkSMMessages for debugging purposes. And I don't know what else to do so that the custom client's camera will be affected. Peter 2016-06-07 16:58 GMT+02:00 Utkarsh Ayachit <[email protected]>: > See pqServer::processServerNotification() [1]. You'll need to call > vtkNetworkAccessManager::ProcessEvents(..) "on idle" to process events > being received from the other client. > > > [1] > https://gitlab.kitware.com/paraview/paraview/blob/master/Qt/Core/pqServer.cxx#L376-401 > > On Tue, Jun 7, 2016 at 8:54 AM, Peter Debuchev <[email protected]> > wrote: > > Hello, > > I have attached a short custom client example which I would like to > always > > show the same perspective as a ParaView session connected to the same > > pvserver. > > > > However, although this example renders once the objects that are > available > > in the ParaView session, it does not update itself when the camera is > > changed in ParaView, despite of the line > > "collaboration->FollowUser(collaboration->GetMasterId());" (see attached > > code). > > > > Apparently I am missing one important step, maybe register the view with > > some proxymanager, call some *::AddObserver(...) or something similar? I > > don't know and couldn't find out after several attempts to understand > > ParaView with the help of a debugger. > > > > As a side note: collaboration in the other direction runs successfully. > If I > > choose ParaView to follow this custom client by double-clicking on the > eye > > symbol in the collaboration panel, then the ParaView view always displays > > the same perspective as the custom client. > > > > Which are the missing steps to have the client update its view, when the > > (master) ParaView camera changes? > > > > Steps to reproduce: > > + compile attached main.cxx > > + run "pvserver --multi-clients &" > > + run "paraview --server-url=cs://localhost:11111 &" > > + create a simple pipeline in paraview > > + run "./main" -> same pipeline as in paraview is rendered in custom > client > > + interact with view in ParaView -> client view does not update although > it > > is expected to follow the master > > > > Peter > > > > _______________________________________________ > > 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 > > >
_______________________________________________ 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
