In my update loop I should do two things now:
1. Update the entities. Somehow I should link this with the controller of each specific entity.
2. Render the entities. I do NOT want the entity to contain render-information, but somehow I need to know what sprite to render or what renderer to call when looping through the entity list.
As i practice application-dev with MVC, i set entity/objectmodel/viewmodel as passive object, mean they not perform/trigger display render.
The render task run by View method. Every entities passed-down by Controller to View.
So if i want to render an object/entity, i just add it into list of objects in Controller to be passed-down to View.
Other way, maybe can use a flag, set inside an object/entity, statement to display or not,
but still that entity will be passed-down to VIew, and it will be checked there for visibility (sure can be a waste).
That's what i thought, at this moment, so far.. Of course there are tons of approaches you can try.
Back then, as the others asked too, what is your main purpose to apply your game program into MVC structure ?
As i see that game program is running more active, mostly, than a form application,
perhaps i need to code the mechanism as short/direct as possible,
to considering balance between execution performance(memory issues) & code structure management.