Peter, If Mach-II doesn't have a view queue then how does it know which view to include next? In other words, how is Mach-II iterating over the view-pages set in each event-handler? I've been scouring over the framework files all morning and cannot seem to locate the logic that specifically handles the views except the displayView function. I see that there are actually two displayView functions defined and both are passed an event object and a view name, but I cannot determine where the view name is derived from. It seems like the framework would have to know that for any given event, some number of view-pages have been defined and that it needs to iterate over those views in order to pass the view name to the displayView method. Can you help me better understand this fucntionality or point me to a resource where I can get caught up-to-speed?
Thanks in advance... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to Mach-II for CFML list. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/mach-ii-for-coldfusion?hl=en SVN: http://greatbiztoolsllc.svn.cvsdude.com/mach-ii/ Wiki / Documentation / Tickets: http://greatbiztoolsllc.trac.cvsdude.com/mach-ii/ -~----------~----~----~----~------~----~------~--~---
