Hi Allen,

Allen Bierbaum wrote:
> 
> Understood, but what field containers really require this before you
> start using them?  In other words, what guidelines are there for
> when/if you need to call commitChanges?

There can be no real guidelines that are optimal, as it depends on the 
code of the FC which dependent data is invalidated/updated. Right now 
it's primarily the bboxes, but I would not depend on it.

The only rule that is safe is that after writing any FC before you can 
read data from and FC again you need to call commitChanges. So 
essentially you can do as many writes as you want, but before you do any 
reads you need to call it, to allow the system to invalidate or update 
dependent data.

So you do need to call it fairly often to be safe. It's probably not 
that much of a problem, as commit is not very expensive. We just can't 
do it automatically for situations like iterating through all vertices 
or normals of a geometry, because for those very light-weight operations 
it would become expensive.

In practice you can get away with a lot less of them, if you know 
whether a variable is dependent on other data or not. The problem is 
that there is no way to see that right now, without looking at the 
complete system.

One way to avoid that would be to add information about a field being 
dependent or independent to the fcd and showing it in the documentation 
somewhere. Not sure if we can use that information in the code, too, but 
  for the documentation it would be useful. See also my other mail 
concerning documentation.

Yours

        Dirk

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to