The odk-instance-first-load event combined with the setvalue action make it possible to define dynamic defaults that will be evaluated once when a new form instance is created. However, this mechanism doesn't allow for dynamic defaults set when new repeat instances are added because those instances …

[image] LN: make it possible to define dynamic defaults that will be evaluated once when a new form instance is created Not to derail anything, but... is there any reason we couldnt simply use the existing once() for this purpose? Its actually probably exactly the assumed behavior of once() […

To be explicit, you are suggesting an alternative to both this and XLSForm spec proposal: add syntax to make it easy to use a value from the last saved instance which is to change the semantics of once() from running when the context node's value is empty to once on instance first load and to use th…

[image] LN: Did y'all discuss your alternative suggestion by any chance? Yeah, bit last minute... sorry. :disappointed_relieved: It only just occurred to me when re-reading stuff before the meeting. once() has been nagging at me for a while, and I think it just 'clicked'... I wanted to run t…

Your proposed plan of action sounds good. I'd like to wait for a plan on how repeats will be handled before moving forward on implementation, though. I'll be very interested in hearing your thoughts on the narrow odk-new-repeat (or other name) that I've described above. [image] Xiphware: Agree…

[image] LN: I'll be very interested in hearing your thoughts on the narrow odk-new-repeat (or other name) that I've described above. Can you wait till the 11th hour, again? :grin:

Thanks a lot for this proposal! Wrt the event name odk-new-repeat sounds good to me. [image] LN: One odd case I'm not sure about is when repeat instances are part of the original form definition (e.g. when jr:template isn't specified. The repeat insertion event would not be fired for those so …

Thanks as always for your thoughtful comments, @martijnr . :heart_eyes_cat: [image] martijnr: I think this new event would allow us to deprecate jr:template (since it's only raison d'être is defaults)! Agreed! [image] martijnr: If a template is not there the implicit template is the empt…

[image] LN: Probably the repeat creation event would get fired for all of those at the time of primary instance load? Do we need to consider any broader ramifications of this; that is, firing various (other) events as a consequence of what happens to already be in the initial primary instance…

[image] Xiphware: I could potentially see that you should also fire an initial xforms-insert on basis of the primary instance existing itself (which I dont think we were proposing, or were we?) Agreed that firing an event for repeat instances that are already in the instance is not ideal. I d…

<setvalue event="odk-new-repeat odk-instance-first-load" ref="age" value="../../my_age + 2" /> Can you point me to an (W3C?) example where multiple events in a single handler are listed like this? I've not found one yet, and just want to confirm this is legit [not that it probably matters, ala "...…

ODK Forum

XForms spec proposal: add event fired when new repeat instance is created

Development

spec-proposal, odk-xforms

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled

Looking for a better way? Try ODK Cloud, the official managed hosting service from the creators of ODK.