Athelbras Posted May 19, 2015 Share Posted May 19, 2015 Anyone know if there is a "proper" way to handle error conditions in a fomod ModuleConfig.xml installer script? What I'd like to have happen when an error is detected by the script is for the Finish button to become disabled, or no longer be present with only the Cancel button remaining. Or else have the install process be completely aborted. Looking through the various tutorial information does not reveal a way to do that. Is there some defined means? Such as setting a predefined flag variable, or calling some function? As is, I simply inform the user that an error occurred and explicitly state that Cancel should be clicked. If the user instead clicks Finish, another message appears which restates that an error occurred and that Cancel should be clicked. If Finish is clicked yet again ... then the installer deliberately tries to copy a non-existent file called Error.txt ... which results in a failed (and thus aborted) install for FOMM (hooray!), but which NMM blithefully skips over and so concludes with a bogus successful install (boo!!!). So suggestions, insights, etc. all happily accepted ... Link to comment Share on other sites More sharing options...
RoyBatterian Posted May 19, 2015 Share Posted May 19, 2015 Hrm it has logical functions in the xml language no? Link to comment Share on other sites More sharing options...
Athelbras Posted May 19, 2015 Author Share Posted May 19, 2015 Not sure how that is applicable to the issue at hand ... expand on your thoughts? Link to comment Share on other sites More sharing options...
RoyBatterian Posted May 20, 2015 Share Posted May 20, 2015 set it up so if there is an error to use a logical and to check the condition and disable the finish button? Link to comment Share on other sites More sharing options...
Recommended Posts