Allow dangerous features after nag screen confirmation
Posted: 2017-01-12, 08:26 UTC
There are many things like one mentioned here (this allowed in Explorer but not planned to ever be allowed in TC) because considered too dangerous (quick search on this word in Suggestions and Behaviour will not be changed forums will bring many of such artificial TC limitations).
I suggest a number of protections allowing only experienced users to use such risky features:
1. add two parameters to wincmd.ini:
AllowRiskyActions=(0/1/2)
IKnowWhatIDo=N (N is a sum of numbers each responsible for certain dangerous action)
If AllowRiskyActions=1 and IKnowWhatIDo is present, the second one will be removed after closing TC. This will allow to do certain dangerous tasks and forget about possible risks after TC restarts. AllowRiskyActions=2 may permanently allow dangerous actions, being highly not recommended setting.
2. If AllowRiskyActions is not 0, pop up a nag screen ("Yes/Yes for this task/No" or random "1-2-3" for confirmation) each time user trying to do tasks with dangerous actions set with IKnowWhatIDo parameter. With no ability to disable such nag confirmation via wincmd.ini or any other way.
3. On very first TC run on a system, if it detects AllowRiskyActions or
IKnowWhatIDo in settings file it may with nag screen recommend user to remove those settiong to make sure user will add them on his own will. This will help in case when this feature has been enabled by pack makers.
I suggest a number of protections allowing only experienced users to use such risky features:
1. add two parameters to wincmd.ini:
AllowRiskyActions=(0/1/2)
IKnowWhatIDo=N (N is a sum of numbers each responsible for certain dangerous action)
If AllowRiskyActions=1 and IKnowWhatIDo is present, the second one will be removed after closing TC. This will allow to do certain dangerous tasks and forget about possible risks after TC restarts. AllowRiskyActions=2 may permanently allow dangerous actions, being highly not recommended setting.
2. If AllowRiskyActions is not 0, pop up a nag screen ("Yes/Yes for this task/No" or random "1-2-3" for confirmation) each time user trying to do tasks with dangerous actions set with IKnowWhatIDo parameter. With no ability to disable such nag confirmation via wincmd.ini or any other way.
3. On very first TC run on a system, if it detects AllowRiskyActions or
IKnowWhatIDo in settings file it may with nag screen recommend user to remove those settiong to make sure user will add them on his own will. This will help in case when this feature has been enabled by pack makers.