Data loss prevention: Difference between revisions
From FreeMind
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
==Preventing accidental deletion== | ==Preventing accidental deletion== | ||
=== Deleting nodes and branches in FreeMind === | |||
Since version 0.8.0, it is possible to delete a whole branch of nodes by pressing DELETE. When a user accidentally presses DELETE and does not notice that, they may loose considerable amount of data. For users using FreeMind as a knowledge base or a semi-structured database, being able to delete whole branch at one keystroke is problematic and unusual; in filesystem browsers, users are asked for confirmation before the file is deleted by the system. | |||
However, some users use FreeMind as a mind mapper and are glad to be able to delete nodes just by pressing DELETE. | |||
There are several solutions to this problem. | |||
* Add user option to enable or disable confirmation before deleting of nodes and branches (depending on model type) | |||
* Store all deleted nodes and branches in a kind of trashcan associated with every mind map | |||
* Ask for confirmation only for nodes with children | |||
* Ask for confirmation only for nodes with more than ''p'' children | |||
The confirmation would be requested both for keystrokes DELETE and CONTROL + X, that is the actions Delete and Cut. | |||
[[Category:Development]] | [[Category:Development]] | ||
Revision as of 10:08, 28 October 2007
Automatic saving of backup copies
Todo
Preventing accidental deletion
Deleting nodes and branches in FreeMind
Since version 0.8.0, it is possible to delete a whole branch of nodes by pressing DELETE. When a user accidentally presses DELETE and does not notice that, they may loose considerable amount of data. For users using FreeMind as a knowledge base or a semi-structured database, being able to delete whole branch at one keystroke is problematic and unusual; in filesystem browsers, users are asked for confirmation before the file is deleted by the system.
However, some users use FreeMind as a mind mapper and are glad to be able to delete nodes just by pressing DELETE.
There are several solutions to this problem.
- Add user option to enable or disable confirmation before deleting of nodes and branches (depending on model type)
- Store all deleted nodes and branches in a kind of trashcan associated with every mind map
- Ask for confirmation only for nodes with children
- Ask for confirmation only for nodes with more than p children
The confirmation would be requested both for keystrokes DELETE and CONTROL + X, that is the actions Delete and Cut.
