On Wednesday, July 20, 2011 10:05:11 AM UTC-4, Iceberg wrote: > > Hi Anthony, > > I encounter same problem. STFW and I read your two posts. One is > above, the other is here: > > http://groups.google.com/group/web2py/msg/25bd655665bf47bf > > I am curious to see a bug exists for 2 weeks. That is not normal, > considering web2py has a tradition of fixing bug within 24 hours. Is > there anything special about this one? Thanks in advance. > > Regards, > Ray (a.k.a. Iceberg)
I submitted a patch for a quick fix, but there are some conceptual problems with non-ajax components that need to be thought through, so I think Massimo may have postponed applying the patch until we figure that out. For example, the fix for this particular issue would involve copying response.generic_patterns to other_response.generic_patterns (which is the response object used by the component). But what if the parent page action made changes to response.generic_patterns -- should those changes propogate to the component (which is what would happen with the simple fix), or should the component not see those changes (that's a lot harder to work out without re-running the models)? Note, this issue is not limited to generic_patterns. Also, I think Massimo has just been very busy the past couple weeks, so there haven't been a lot of commits in general. Anthony
