View Single Post
Old 09-19-2024, 11:10 AM   #175
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,701
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
The good news is that the configs are being saved with the actual text/tag parameters, so in a headless run (and any potential minimal GUI run), things should just work. No validation needed since the validation takes place before the config can get successfully saved.

The challenge will be in loading the saved config into a full GUI run. There will need to be some sort of validation that maps text values to indices to make sure things have not been altered in the plugin customization that would cause combobox indices to change. And there would need to be something done to handle the situation where something in a saved config was subsequently removed from the plugin customization fields. Probably a rare situation -- but still possible.
DiapDealer is online now   Reply With Quote