[Bf-taskforce25] unique integer ids for ID types

[Bassam Kurdali]

would be pretty cool, could solve issues for e.g. when changing a name
in a bone/object that happens to be a target for constraints, etc. if
the actual target (stored internally of course) is the id and not the
name.

On Thu, 2009-06-11 at 07:13 -0600, joe wrote:
> I had an idea the other day.  What if we store a unique integer id
> (uid) in ID blocks, bones, nodes, etc?  This would solve a number of
> issues, as I see it:
> 
> 1. RNA paths would be faster and more reliable to resolve.  If you
> rename an object, or a bone, or a material, the uid stays the same, so
> there's no need to go through and update existing RNA paths.  And
> looking up integer uids would be much faster then looking up names.
> 2. Things without names (e.g. nodes) require something like this,
> since basing the RNA paths off of simple indices would be far too
> unstable.
> 3. This might work for constraint targets, too; e.g. the constraint
> would store a uid, but present the user with the same UI of typing in
> a bone's name, of course.  This idea would probably need more thinking
> through, however.
> 
> Joe
> _______________________________________________
> Bf-taskforce25 mailing list
> Bf-taskforce25 at blender.org
> http://lists.blender.org/mailman/listinfo/bf-taskforce25
-- 
PGP public key http://freefac.org/misc/public.key