Hi, sorry for the delay, I was travelling.
On Thu, 2010-03-04 at 11:05 +0100, Volker Settgast wrote: > On 26.02.2010 04:52, Gerrit Voß wrote: > > > .... > > > For a clusterServer we first set the server-specific values, > > > like surface, left/right-eye in the ClusterWindow prototype. > > > Then the Client just opened the ClusterWindow and the settings > > > were allready good for all servers. How would You handle such > > > a setup? > > > > > that might be a very very old leftover, looking at it something is odd > > and looks unfinished. > > > > Are you modifying the prototype or are you replacing it. Purely > > modifying should still work as the getPrototype is still there. > > > > I'll have a quick check and try to remember why it was left unfinished > > and put the set function back in if I don't spot anything. > > > > > > > Hello, > > so I tried to modify the prototype by calling getPrototype, casting > the pointer and setting fields. But either I do something really > wrong, or it just does not work: > > example: > FieldContainer* test = > MatrixCameraDecorator::getClassType().getPrototype(); > MatrixCameraDecorator* > matrixProto=dynamic_cast<MatrixCameraDecorator*>(test); > matrixProto->setPostProjection(calibMatrix); > > > As You can see, I want to set different decorators for cluster > servers. The other way would be to catch the first frame in the server > and then change the fields. Any other ideas? this is done on the servers, but the MatrixCameras it should apply to are created on the client and are than transmitted ? In this case the problem would be that what you set in the prototype will be overridden by the cluster transfer. E.g. after creating the camera on the server it receives data from the client. As all fields are marked as to be transmitted on the client (this changed from 1.x) what you should find is that all server elements contains the client data. What you would have to do is to mark the fields you do not want to be transmitted. There are (in principle) two ways to do this, either mark them as ClusterLocal, which means no changes on the client will be transmitted, or mark them so that during the creation the field is not flagged for transmission. Currently both ways are only available through the fcd mechanism. I'll update the interfaces and get back once the changes are committed. kind regards gerrit ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Opensg-users mailing list Opensg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensg-users
