A middle may be, a button to save preferences, spaced well away from the existing buttons.
The theory being -
if save preferences is never clicked Lite Tweaks will work as it does now.
if 1 item is ticked and save preferences is clicked, on the next run of Lite Tweaks, it will be pre ticked.
If on that second run another item is ticked and save preferences is also clicked, for that run and future runs it pre ticks the 2 items.
eg it permits all numbers of allowable ticks (safe ones) not only 1 or 2.
Where extra rows are ticked and save preferences is not clicked it will run those rows on that instance of Lite tweaks only, thus allowing not safe rows to be ticked and run as usual.
On the next turn if both are unticked and save preferences is clicked it returns to Lite Tweaks as it works now, it's the failsafe/reset method for the preferences and Lite Tweaks.
It would for example be good if it only allows save preferences of rows that are "Safe", acting as a safeguard to stability.
I wouldn't know how to create the code, it could work (the theory) ?
- in safe rows and/nand (and it is ticked, not and it isn't ticked), in the not safe rows exempt from the save preference button it could use NOP, jump (to the next row).
The theory being -
if save preferences is never clicked Lite Tweaks will work as it does now.
if 1 item is ticked and save preferences is clicked, on the next run of Lite Tweaks, it will be pre ticked.
If on that second run another item is ticked and save preferences is also clicked, for that run and future runs it pre ticks the 2 items.
eg it permits all numbers of allowable ticks (safe ones) not only 1 or 2.
Where extra rows are ticked and save preferences is not clicked it will run those rows on that instance of Lite tweaks only, thus allowing not safe rows to be ticked and run as usual.
On the next turn if both are unticked and save preferences is clicked it returns to Lite Tweaks as it works now, it's the failsafe/reset method for the preferences and Lite Tweaks.
It would for example be good if it only allows save preferences of rows that are "Safe", acting as a safeguard to stability.
I wouldn't know how to create the code, it could work (the theory) ?
- in safe rows and/nand (and it is ticked, not and it isn't ticked), in the not safe rows exempt from the save preference button it could use NOP, jump (to the next row).