h a l f b a k e r y
We have a low common denominator: 2
add, search, annotate, link, view, overview, recent, by name, random
news, help, about, links, report a problem
or get an account
Please log in.
Before you can vote, you need to register.
Please log in or create an account.
When working with Windows, you often do things which you haven't done before, and are not completely sure about. The common practice when doing such things is to save backups of data and use "undo's" for backtracking. The problem becomes more complicated when you are not aware of all the possible consequences
of your action and therefore you rely on the system backtracking capabilities. In XP for example there is the "Last known good configuration" which helps you recover from system boot failure.
What I'm suggesting here, is a "taking risk" mode, which tells the system or any application to take extra care about the activity, and to enhance the logging and reporting of what went on since entering that mode.
My feeling is that keeping a uniform level of "undo" possibilities takes alot of resources on one hand, and doesn't always help you when you really need it, on the other.
||You only really need undo when something really big happens and then normally the application has a memory oveload anyway and the machine Blue Screens.
||Some early software used to have an Advanced menu option to stop idiots from accessing functionality that they shouldn't be allowed to see. Sounds a lot like that.