Philip Rieck wrote:
Sam,
NameObjectCollectionBase's underlying type is a Hashtable, not an ordered
Philip,
Thanks for the suggestion. I did a bit more reading on the collection
classes available, and tried a few things....
The more I looked, the more I learned that the collections classes
provided seem broken into to categories: Those that are index-based
(collection, etc) , and those that are Key-based (dictionary, etc).
Other than the legacy vb6 collection, there doesn't seem to be a single
collection that supports both indices and keys natively. The vb6 legacy
collection served me well (supporting objects, keys & indices) until the
day I needed serialization (which it does not support); hence my journey
here.
As you suggest, I could wrap my objects with another property such as an
index value, and maintain that value along with all changes to the
collection. However, I'm concerned about the amount of time it would
take to "ripple" changes through large amounts of those indices when
deleting, inserting, etc. a new value into the collections. Not to
mention that locating items further along in the collection will take
longer than sooner in the collection. My collections can consist of
several thousand objects.
I'm continuing to experiment with this......I look forward to any other
suggestions you might have!
--
================================================== ================
Sam J. Marrocco
Sr. Visual Effects Artist/R&D
Travelling Pictures/GTN
Inferno, Flame, Maya, All that cool stuff!
"The fact that no one understands you doesn't make you an artist."
================================================== ================