A User contacted Chris Legualt that new cases in version 4.3.0.0 do not save to file.
At initial glance this issue may have been caused by missing documentation or unintended input. However, with further testing, it seems that the gui's new case values input store are not data binded to PIFSCstockassessments/AGEPRO-Corelib when new cases are created via SET button in General Options.
I have to find if there more to this issue than just missing Data Binding.
Edit 11/21/2018: I isolated the causes of this issue:
- New case values are initialized with NULL values.
- An issue where Binded values (Bootstrap Filename, misc options, Stochastic tables) wasn't updating.
- Lack of NULL checks implemented when writing AGEPRO Input Files.
- Null errors were not properly passed to the GUI.
- Allowed to program to continue, but stopped writing to file with out a explanation.
Solution
This is what I implemented or is currently implementing to deal with this issue:
- Implicitly set new case values during initialization (When user submits the General Options 'SET' button).
- Add Dialog box that new case has been properly Initialized.
- Tweaked the binded values updates to
OnPropertyChanged
- Re-Throw AGEPRO-CoreLib errors to GUI.
- Implemented Null Checks. Add the AGEPRO
[PARMETER] to NULL error msg to indicate which one has NULL input.
A User contacted Chris Legualt that new cases in version 4.3.0.0 do not save to file.
At initial glance this issue may have been caused by missing documentation or unintended input. However, with further testing, it seems that the gui's new case values input store are not data binded to PIFSCstockassessments/AGEPRO-Corelib when new cases are created via SET button in General Options.
I have to find if there more to this issue than just missing Data Binding.
Edit 11/21/2018: I isolated the causes of this issue:
Solution
This is what I implemented or is currently implementing to deal with this issue:
OnPropertyChanged[PARMETER]to NULL error msg to indicate which one has NULL input.