Done. I personally prefer zero='' as a default. I think the selection should be made explicitly by the user unless an actual default value for the field is set. This doesn't break backwards compatibility IMO because web2py wasn't controlling it before, the browser was.
On Mar 21, 8:26 pm, Thadeus Burgess <[email protected]> wrote: > That is not a good point. That is a interface and usability question, > also it is a clientell question of who will be using the app. > > I am tired of arguing this matter. As far as I see it, we broke > backwards compatibility, forcing me to update all of my apps. > > I respectfully ask the community to please take the following > anonymous survey on this topic. I will support the outcome of the > results for this survey as the community decision. > > I will not take part of this survey since I created it. > > https://spreadsheets.google.com/viewform?formkey=dE5pd01zNndEMk4zREpF... > > -Thadeus > > On Sun, Mar 21, 2010 at 7:55 PM, mdipierro <[email protected]> wrote: > > Not everybody agreed. Somebody (do not remember who) made a good point > > that having zero=None will case people to fill forms with with wrong > > values (always the first alphabetical value). > > > On Mar 21, 7:21 pm, Thadeus Burgess <[email protected]> wrote: > >> Massimo, I think in the post everyone agreed to make zero=None the > >> default, and yet after at least 13 of us said to make this the > >> default, nothing happened. The original design was (is) a good idea, > >> but making that a default was a bad idea. Nobody had any input at the > >> moment, but after playing around with it, it sucks being the default. > > >> -Thadeus > > >> On Sun, Mar 21, 2010 at 1:00 PM, mdipierro <[email protected]> wrote: > >> > There was a long discussion about this. Different people disagreed on > >> > how this should behave. > > >> > You can revert to the previous behavior with > > >> > IS_IN_SET(...,zero=None) > >> > IS_IN_DB(...,zero=None) > > >> > Or customize the empty value > > >> > zero="Please choose one" > > >> > Massimo > > >> > On Mar 21, 12:42 pm, annet <[email protected]> wrote: > >> >> Today, I upgraded my web2py installation to version 1.76.5. In this > >> >> web2py version the drop boxes display an empty key value pair first, > >> >> and then the key value pairs from the tables I based them on. What > >> >> causes this change in behaviour? How do I correct it? > > >> >> Kind regards, > > >> >> Annet. > > >> > -- > >> > You received this message because you are subscribed to the Google > >> > Groups "web2py-users" 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 > >> > athttp://groups.google.com/group/web2py?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "web2py-users" 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 > > athttp://groups.google.com/group/web2py?hl=en. > > -- You received this message because you are subscribed to the Google Groups "web2py-users" 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/web2py?hl=en.
