Hi All,
Carsten Neumann wrote:
>> the priority just an assigned value, e.g something like 10 for time
>> sensors and 50 for blenders. The change is from the last time sensor
>> (prio 10) to the first blender (prio 50). The effect is that it is
>> guaranteed that after all time sensors are done, commitChanges
>> is called so the time sensor values are propagated to the blenders
>> before their eval function is called.
>
> yes, this part is not in the patch yet, but I like it.
>
> What do you think?
I'm not a big fan of it, as it can make combining things harder and it needs to
be set up manually. I'm not sure how you would do it for an arbitrary VRML
input, which can have routes going all over the place. It's just not the "Right
Thing To Do" (TM). ;)
But on the other hand I'm prone to ignore 'Worse is Better', so we might take
it
as a first shot and wait fro it to break before going fancy (as a general
solution needs to get pretty fancy indeed...).
Just my $.02
Dirk
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
