Hello Michael,
On 03/09/2011 01:02 PM, Michael Raab wrote:
> thanks, both hints worked. The callback gets now called as expected.
> Remains the problem, that if I update the ShaderParameter via
> setValue(), the appropriate changes are not applied as the
> ParameterField of the SHLChunk gets not marked as changed.
> The callback function provides only a pointer to the ShaderParameter,
> theres no connection between Parameter and SHLChunk. Do you think it is
> possible to deliver both, the ShaderParameter and the SHL as parameter
> of the callbacks? Do you see any drawbacks?
hmm, I don't know who else is using the callbacks, but it would break
their code if you change the prototype for the parameter callbacks...
> Second question. I saw that if a add a callback for a specific parameter
> that does not exist, a dummy parameter is created. Is that necessary?
I'm not sure I understand what you mean with "a specific parameter that
does not exist"? Before you've added them they all don't exist, no?
Sorry, I'm sure there is something I'm missing...
> So
> in my case, if a add a callback to each SHLChunk that gets created, each
> chunk tries to update each frame, independent of whether we assigned a
> timer variable or not. That may be not very fast...
Hmm, well the callbacks where meant for stuff that changes a lot (some
of the existing ones change even more often, e.g. the ModelViewMatrix)
and the timer variable would normally change its value from frame to
frame anyway, wouldn't it?
Cheers,
Carsten
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users
