Anthony, Yes I see, and Massimo's suggestion to backport the superior helpers from Web3py is probably better than making changes to the existing code. However, thanks very much for explaining this effect. D
On Tuesday, 4 June 2013 16:36:42 UTC+1, Anthony wrote: > > On Tuesday, June 4, 2013 10:04:46 AM UTC-4, villas wrote: > >> Very interesting explanation, but it still seems obscure and not the >> kind of thing the average user would consider. Isn't there an easier way >> to make this work as expected? >> >> For example, shouldn't differently named SELECTs be parsed independently >> from each other? >> > > In this specific case, that would certainly make sense, but perhaps not in > the general case. Sometimes when you re-use a mutable object, you do want > changes made in one place to affect the other contexts. Suppose instead you > need to dynamically change the value/label of the third option and you want > that change in all of the SELECTs -- in that case, you just change the > "items" object once. The problem here is that it is not transparent that > when you set the "value" argument of SELECT, it is actually changing the > attributes of the OPTION objects nested within the SELECT. I'm not sure > what the best approach would be. > > Anthony > -- --- 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/groups/opt_out.
