I wouldn't say the use case is odd but it's definitely complex. Then again, without a context for custom widgets to operate in (i.e. no knowledge of the record or form that they are bound to) only simple use cases are possible. Represent and widget are output/input analogs but for some reason represent has access to the whole row whereas widget only gets the field value. I will propose a patch if it can be done unobtrusively and without coupling Field to SQLFORM any further.
On Sunday, October 27, 2013 6:10:22 PM UTC-5, Anthony wrote: > > Thanks, Anthony. I am doing something similar by setting a session >> variable so that it will work in appadmin forms too. I wonder why widgets >> don't get the record since the represent function does. Seems like an >> oversight. > > > The "represent" attribute is specifically for displaying the values of a > given record, whereas the widget is for creating a form input. Although a > widget may display a default value (e.g., when editing a record), in most > cases you want that to be the actual raw value that goes in the database, > not some alternative representation. Sounds like you might have an odd use > case. > > 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
