I will expect the behaviour to be this: 1. If the form field is pre-populated with data A AND visualized, the visualized field should be populated with the data A, then data A should be accepted with the rest of the form data. Unless data A is amended by the user, then the amended data is accepted.
2. If the form field is pre-populated with data A AND NOT visualized, data A should be accepted with the rest of the form data. Am I getting this right? maurice On Feb 11, 4:15 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > I will look into changing its behavior. This can be seen as a bug fix > but also as a backward compatibility issue. Anybody opposes? > > Massimo > > On Feb 10, 1:20 pm, DenesL <denes1...@yahoo.ca> wrote: > > > Fixing the manual is easier but what does form.vars.field=value really > > do then?. > > > A fixed form.vars.field would have multiple personalities. > > It would act as db.tablename.fieldname.default if the field is shown > > in the form and as request.vars.field if it is not returned by the > > form. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
