If you find this article contains errors or problems rendering it unreadable (missing images or files, mangled code, improper text formatting, etc) please contact the editor so corrections can be made. Thank you for helping us improve this resource
© 2000 - Zachary Booth Simpson. Copied with permission from http://www.mine-control.com/zack. If you find any of this work useful, please sign Zack's guest book: http://www.mine-cont...i/gbook-zbs.cgi. Intent
Pass-off special render cases to Model code. Problem
Generic View code often becomes clotted with special cases, especially near the end of a project. Render Delegation gets the special cases out of the View code and into Model subclasses. Solution
An example clot in View code: Structure
drawSpecialShieldEffect();To encapsulate these kinds of special cases, the View delegates the draw back to the Model. For example: objectToDraw->draw(x,y)
It is common for the view to do the transformation and sorting work and pass screen coordinates to the draw method of a model.
Not available at this time. Examples
No examples at this time. Email email@example.com to contribute. Issues and Risks
Use Render Delegation when: Related Patterns
Don't use Render Delegation when:
- You want to ensure reusability / encapsulation of the renderer.
- The View code becomes clotted with special cases.
- Every model tends to have a different implementations of render.
- There are only a few special cases and the cost (compile time, encapsulation) of including render interfaces in Model code is very high.
Render Delegation passes draw commands from View to Model.
Render Delegation may be part of an Appearance Map.
Note: GameDev.net promotes a collaborative environment.