Whoops - forgot to note, in the case FOR "no-null-call", that a
serious problem comes up with {{{for-template|multiple}}} whenever the
template does NOT contain any mandatory fields. If the user selects
"Add another", but does not "Remove" it before saving the page, then
an empty call is being inserted into the page. Of course, whenever the
page is re-edited, those empty fields are displayed again. I hafta
think that's clearly a bug -- the user in this case had no intention
to create a new instance of the template and its fields, the user
simply forgot to "Remove" it before saving the page.Which of course brings back to mind that default values cause problems detecting when a user has forgotten to "Remove" an empty/unwanted template repitition, because those fields with defaults automatically translate into template args.... so I have to conclude that "no- default-arg" remains important to me, in order to address this highly understandable "mistake" by the user, while preserving default values in repeating templates. So that's the use case for "no-default-arg" that I'm most concerned -- if you know how I can otherwise deal with this, that'd be great - thanks! [ok, i'll be quiet now!] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Semantic Forms" 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/semantic-forms?hl=en -~----------~----~----~----~------~----~------~--~---
