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
Is your feature request related to a problem? Please describe.
This would assist with the auto-updating/updating of extended.conf, as well as prevent #189 from happening again.
Describe the solution you'd like
To implement this feature, there would need to be 2 things done:
Update extended.conf from its current format to an "ini' file type format. It's already very close.
Go from:
To:
This would allow easy parsing of the conf file, by other languages (already have it working in Python).
On startup, a python script can parse the local conf, download the current repo's conf, compare the two, and add any new values missing.
This could either update the user's conf on each restart, or it can be the new/alternate way to update the conf file by running the py script. If it is done on start, I believe the script would need to be called by setup.bash, for the changes to happen before the other scripts start up. A flag can also be added to extended.conf so the user has the option to turn this off.
Risks:
Wiping out the user's extended.conf.
Transferring users' format to ini format. This would have to be pushed somehow. I suppose I could use the current format, but it may be cumbersome to parse (currently how it is in ARLChecker).
I understand this is a somewhat risky change. Thoughts appreciated!
Flow chart:
The text was updated successfully, but these errors were encountered:
Better than having the Kodi script and renaming features turn themselves on randomly without warning and having all your content unexpectedly renamed and changed
Is your feature request related to a problem? Please describe.
This would assist with the auto-updating/updating of extended.conf, as well as prevent #189 from happening again.
Describe the solution you'd like
To implement this feature, there would need to be 2 things done:
Go from:
To:
This would allow easy parsing of the conf file, by other languages (already have it working in Python).
This could either update the user's conf on each restart, or it can be the new/alternate way to update the conf file by running the py script. If it is done on start, I believe the script would need to be called by setup.bash, for the changes to happen before the other scripts start up. A flag can also be added to extended.conf so the user has the option to turn this off.
Risks:
I understand this is a somewhat risky change. Thoughts appreciated!
Flow chart:
The text was updated successfully, but these errors were encountered: