Thanks again Anthony, To be honest that's a bit beyond my abilities at the moment though plenty of food for thought! I think I have a work around... essentially by doing the person search before building the list for the grid. i.e I can identify the person first and add person.id it to the query filter, my view will only present activities belonging to the person negating any need to search by person.
Peter The simplest alternative might be to use a computed field. Alternatively, > you could further develop your approach of adapting the db.task.person > field for your purposes. For that to work, you would have to implement > custom search functionality (the "searchable" argument can be a function > that generates a custom search query, and the "search_widget" argument can > be a custom search widget for the UI). If you want proper sorting, you > would also have to intercept sorting requests and override with a custom > "orderby" argument. > > Anthony > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
