I've gone through all my widgets, and none of them use local variables that would require re-instantiating the widget to update.
I've also noticed that if I reduce the number of threads used by the server to 1, the problem goes away. Alternately, if I use 3 threads, it usually take 2 refreshes for changes to show up, so it seems that this has something to do with either communication between threads or communication with the sql server. Does SQLObject have some setting which forces it to re-fetch data from the server or something? -Ryan On Feb 12, 10:28 am, kerinin <[EMAIL PROTECTED]> wrote: > The widget execution problem may be what's causing this - I'll need to > look at how they're working to know for sure. > > -Ryan > > On Feb 12, 3:39 am, Christoph Zwerschke <[EMAIL PROTECTED]> wrote: > > > Jiří Popek schrieb: > > > > This strange behaviour happens to me some times... I found that if I > > > use <?python > block in KID template and define some variables, they > > > doesn't gets updated every time properly... other ways (passing the > > > variable from controller or defining in py:XXX blocks) works just > > > Maybe you put your <?python > block outside the <html> element? Then it > > will be only executed once when the template is loaded. > > >http://www.kid-templating.org/language.html#embedding-code-blocks-python > > > -- Christoph --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
