I would strongly recommend following Matt's advice to review the request lifecyle page, as while the general order of processing is messages, then results, then views, there are a couple of subtleties/exceptions that can trip you up.
One thing that is key to understanding the process is that both events triggered by results and views are queued -- they are *not* processed/rendered immediately (although there are a couple of exceptions in regards to results, which are detailed in the lifecycle documentation). Be sure to let us know if you have any questions, or find anything on the lifecycle page confusing or unclear. -- Ezra On Mon, Jun 7, 2010 at 12:57 PM, Shawn Downs <[email protected]> wrote: > No, I get distracted by sparkly things... > > I think (hope) that I see what you're saying. When that result is true, am > rendering two body and menu views. I thought that my code just said "Instead > of rendering the body you wanted, render the log in screen". I guess that in > the case of PDF's, they load on top of everything regardless but the pdf > information shouldn't be rendering at all. > It seems that I have some reading to do after all :o) > > Thanks, > Shawn > On Mon, Jun 7, 2010 at 3:29 PM, Dan Wilson <[email protected]> wrote: >> >> Shawn, >> Did you turn on the Model-Glue debugging and read the output? This will >> show you exactly the steps taken to process your application and how much >> time each step took. >> I believe when you do this on your event with the PDF CFDocument call, >> you'll see exactly why you get the behavior you get. >> I'd prefer for you to get comfortable with this debug output, rather than >> me just giving you the answer, because you seem like a keen self-learner and >> it will help you understand how Model-Glue looks at your configuration. Once >> you've looked at the debugging, you'll have further questions and I'm >> totally happy to give you the answers. >> >> DW >> >> >> On Mon, Jun 7, 2010 at 3:23 PM, Shawn Downs <[email protected]> >> wrote: >>> >>> The documentation puts the results before the view. This was copied >>> exactly from the docurmentation lined below: >>> >>> Summary/Review >>> >>> The order of execution for event-handlers is: >>> >>> broadcasts >>> results >>> views >>> >>> Am I reading it correctly? In any case, I gather from your comments that >>> my implementation is all wrong. I will look around and see if I can find an >>> example so I can do it better. >>> >>> Thanks, >>> Shawn >>> >>> On Mon, Jun 7, 2010 at 2:50 PM, Matt Quackenbush <[email protected]> >>> wrote: >>>> >>>> For more detail, check out the Request Life Cycle page: >>>> >>>> >>>> http://docs.model-glue.com/wiki/ReferenceMaterials/RequestLifeCycle#RequestLifeCycle >>>> >>>> -- >>>> Model-Glue Sites: >>>> Home Page: http://www.model-glue.com >>>> Documentation: http://docs.model-glue.com >>>> Bug Tracker: http://bugs.model-glue.com >>>> Blog: http://www.model-glue.com/blog >>>> >>>> You received this message because you are subscribed to the Google >>>> Groups "model-glue" group. >>>> 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/model-glue?hl=en >>> >>> -- >>> Model-Glue Sites: >>> Home Page: http://www.model-glue.com >>> Documentation: http://docs.model-glue.com >>> Bug Tracker: http://bugs.model-glue.com >>> Blog: http://www.model-glue.com/blog >>> >>> You received this message because you are subscribed to the Google >>> Groups "model-glue" group. >>> 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/model-glue?hl=en >> >> >> -- >> William Osler - "We are here to add what we can to life, not to get what >> we can from life." >> >> -- >> Model-Glue Sites: >> Home Page: http://www.model-glue.com >> Documentation: http://docs.model-glue.com >> Bug Tracker: http://bugs.model-glue.com >> Blog: http://www.model-glue.com/blog >> >> You received this message because you are subscribed to the Google >> Groups "model-glue" group. >> 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/model-glue?hl=en > > -- > Model-Glue Sites: > Home Page: http://www.model-glue.com > Documentation: http://docs.model-glue.com > Bug Tracker: http://bugs.model-glue.com > Blog: http://www.model-glue.com/blog > > You received this message because you are subscribed to the Google > Groups "model-glue" group. > 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/model-glue?hl=en -- Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog You received this message because you are subscribed to the Google Groups "model-glue" group. 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/model-glue?hl=en
