Custom widgets, response value, and documentation
Posted: Fri Apr 05, 2019 4:25 pm
I've recently been working a bit with learning how the custom widgets work with Profound.
There are couple questions I had regarding the documentation at http://www.profoundlogic.com/docs/displ ... onse+Value
1. For a custom widget, there is an onsubmit function (myCustomWidgetOnSubmit) that must be called via the record format's onsubmit property. Is there a way to have the custom on submit function for our custom widget to be called without manually putting this in the record format's on submit property? While it may not be a big issue, it may not be obvious to someone who did not develop a specific custom widget that they will need to add in that code in the onsubmit property for each record format containing that widget.
2. Is there somewhere we can report possible errors in the documentation? Upon referencing the example titled Example "field type" property setter in the link mentioned above, I ran into an issue. The example attempts to reference id directly, but when I tested this I had to use parms.dom.id to retrieve the correct id for that element.
Thanks
There are couple questions I had regarding the documentation at http://www.profoundlogic.com/docs/displ ... onse+Value
1. For a custom widget, there is an onsubmit function (myCustomWidgetOnSubmit) that must be called via the record format's onsubmit property. Is there a way to have the custom on submit function for our custom widget to be called without manually putting this in the record format's on submit property? While it may not be a big issue, it may not be obvious to someone who did not develop a specific custom widget that they will need to add in that code in the onsubmit property for each record format containing that widget.
2. Is there somewhere we can report possible errors in the documentation? Upon referencing the example titled Example "field type" property setter in the link mentioned above, I ran into an issue. The example attempts to reference id directly, but when I tested this I had to use parms.dom.id to retrieve the correct id for that element.
Thanks