-
-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Persisntance of input field values without property attributes for pdf exports #152
Comments
I have no idea how the PDF export works. I would expect all input fields to display their default values, and the date picker simply defaults to the current date. |
The pdf export is using the default values. This can be seen by changing the default values and exporting to pdf. Something like this works: Could there be a more robust implementation into the plugin to not use this workaround? It can get repetitive if one uses many temporary input fields in cases like tasks management, for instance, where one wishes to be able to export the tasks file as a pdf file for sharing reports. |
so you want input fields to display the correct values (not the default values) in the exported PDF? |
Yes. The selected values export as long as there is a properties attribute for it defined. In cases where there is no unique properties attribute defined, the exporter uses the default value. I don't really know how this could be changed without knowing how pdf export works. Is there a way to pass data to the pdf exported about the selected input fields? |
sounds like the plugin works as intended.
what do you mean with selected input fields? |
The values also disappears if one moves the cursor over the input field code block. |
Unbound input fields can not persist their data, as they have nowhere to store it. |
Is your feature request related to a problem? Please describe.
Exporting to pdf exports the selective fields empty (ex. time input field).
Describe the solution you'd like
It would be great to have the values export to pdf.
Additional context
The text was updated successfully, but these errors were encountered: