You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want users to be able to save the values they select throughout the GUI, and then be able to re-load those values.
We should be able to handle this "automatically" by basically having the button to run the model also cause the values in the input fields to be saved into a standard format csv or the like.
We need to build in the capacity to re-load the inputs, as well. This would, ostensibly, also give someone the capacity to create a setup file externally and then load it in the app and have it populate the input fields, thereby avoiding having to click through everything.
This is definitely doable, but it'll take some solid planning and mapping out of the GUI, which is needed anyway at this point (I need to re-check that all of the values are being created and stored in the best possible manner for this and other stuff).
The text was updated successfully, but these errors were encountered:
this is definitely doable but is a bit more complicated than i can work through for version 1 right now. i need to break down how best to store and retrieve the data dynamically. I have some loose code that works partially using .Rdata files, that i'll include in a development folder, and I think this is something we can get into version 2.
We want users to be able to save the values they select throughout the GUI, and then be able to re-load those values.
We should be able to handle this "automatically" by basically having the button to run the model also cause the values in the input fields to be saved into a standard format csv or the like.
We need to build in the capacity to re-load the inputs, as well. This would, ostensibly, also give someone the capacity to create a setup file externally and then load it in the app and have it populate the input fields, thereby avoiding having to click through everything.
This is definitely doable, but it'll take some solid planning and mapping out of the GUI, which is needed anyway at this point (I need to re-check that all of the values are being created and stored in the best possible manner for this and other stuff).
The text was updated successfully, but these errors were encountered: