2009/5/12 Christopher Sean Morrison <[email protected]>:
>
> On Friday, April 17, 2009, at 02:06PM, "Daniel Roßberg"
> <[email protected]> wrote:
>
>>However, everybody should know an important property of the Object
>>classes in the core interface: They represent copies of database
>>elements. I.e. changing an Object class does not change the database.
>> The Object has to be written back to do this (the call-back method
>>does this automatically). This behavior cannot be changed at
>>coreInterface level. But one could write object classes with
>>automatic write backs on a higher level (on top of the coreInterface).
>
> That's interesting to know, and I'm not sure I understood that from reading
> the sources but I gather that's why there are internal-only objects in use.
> Don't see that as a problem really as the notion of the application always
> being in a saved state certainly is something that should happen at the
> application level and not the library level (hence why librt writes are so
> explicit).
The Objects in the core-interface are representations of the
rt_*_internal structs (especially rt_db_internal). These structures
are filled with rt_db_get_internal() from the database and have to be
written back with rt_db_put_internal() to change the database.
Szia,
Daniel
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
BRL-CAD Developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
