extending ObjectManager?

[Wally]

Hello,
First I want to say Hi everyone on the board, forum is awesome, tutorials are great. I managed to follow tutorials but i have a question regarding ObjectManager.
So i started to code some demo to test drive little engine, and got to a little problem. I changed type for storing objects from Collections to Dictionary, so i can get object from ObjectManager from object name, and that works fine.
But at some point i would like to iterate through every object in my ObjectManager and change some of object properties. Like shaders, putting flags or something.
Now im not sure what is the right way to do this, i doubt making whole Collection public is a good idea. Maybe to put all objects in LinkedList so i can return just first element, and cycle through rest. Anyway I need some advice on this matter.  Thanks in advance.

[mikeschuld]

The Dictionary has a Values property that just returns a list of the actual objects in the collection. Why don't you make a get { return dictionary.Values; } or something similar?

[solthar]

Got me thinking on that, couldn't you just use a foreach to loop through it all?

eg;

Code:

using System.Collections.Generic;

//...

foreach (KeyValuePair<string, HMObject > pair in dictionaryName)
{
    //pair.Key returns string key value
    //pair.Value returns HMObject
}

[mikeschuld]

That's exactly what I meant

Code:

foreach(HMObject object in dictionary.Values){

}

[Wally]

Thank you guys, alot. You own

[Wally]

That's exactly what I meant

Code:

foreach(HMObject object in dictionary.Values){

}

Sorry for double post.Maybe I am missing something and sound ridiculus but i dont see a way going through HMObjects through dictionary because it a list od HMNodes that actually contains my object. I have objManager from Pdf tuts.So i came with this solution.

Code:

foreach(HMObjectNode  obNode in myChildren.Values )
              {
                 obNode.MyObject.Position = ........
             
              }

Since current implementation of manager dont have childs in HMObjectNode i think this would do..