Hello Gerrit,
On 07/03/2011 09:45 PM, Gerrit Voß wrote:
> ok, I committed your old change origin patch,
ok, thanks, especially for catching this:
// I don't think clear is correct here if the apps expects to tap
// into the changes they will be gone (GV)
//pDstCL->commitChangesAndClear(ChangedOrigin::Sync);
I agree, clear is not the right thing to do here.
> for the map in
> shaderprogvars I fixed it so it behaves the same as the local
> MT sync an rebuilds the map if the var fields are changed during
> a sync. I also pushed the map down to ShaderProgramVariables and
> removed the access class as ShaderProgramVariables has taken over
> that part anyway so there should be no need for a separate class
> anymore.
ok, I had mostly kept it separate so that there is a type that can be
put in a SField and synced across the cluster.
> I did some basic testing and it looks ok, the values are
> updated and no warnings are printed.
a quick test here seems to confirm this, I also don't get the warnings
any more.
Thanks & cheers,
Carsten
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Opensg-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-core
