One more comment. If your app is simple enough (most are), to use just one controller, it does not have much difference between define your menu in models/menu.py or at the beginning of controllers/default.py, and the latter gives you most flexibility to control what your menu shows up.
On Jul12, 9:57pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > Hello Casey, > > the problem is models files (including menu.py) are executed > alphabetically before the controller.py. It is possible that your menu > is built before the session variables are updated. This is likely the > case if the session is modified in the controller. > > If only a few functions make changes to the session that should affect > the menu, I suggest rebuild the menu in those controller functions. If > this is a gereral issue, please post an example of how you build the > menu and I'll post an example of how you get it executed after every > controller (as opposed to before). > > Massimo > > On Jul 12, 8:51 am, Casey Schroeder <vizqu...@gmail.com> wrote: > > > > > Hi to all, > > > I had a question: > > > I noticed that when i tried to make my response.menu dynamic, based on > > the values in the session, there was a lag in the update: i.e. I would > > set the session values in the controller for the current page, but the > > menu appears to already be rendered based on the values set on the > > previous page (controller) - even though the current values show on > > the session dump on the current page. To get around this, I just set > > my response.menu directly in the controller, so nbd. I'm just > > wondering if it is always the case for the model files and whether > > there is something else i should look out for because of this. > > > Thanks, > > > Casey
