1 | #Please insert up references in the next lines (line starts with keyword UP) |
---|
2 | UP arb.hlp |
---|
3 | UP glossary.hlp |
---|
4 | |
---|
5 | #Please insert subtopic references (line starts with keyword SUB) |
---|
6 | #SUB subtopic.hlp |
---|
7 | |
---|
8 | # Hypertext links in helptext can be added like this: LINK{ref.hlp|http://add|bla@domain} |
---|
9 | |
---|
10 | #************* Title of helpfile !! and start of real helpfile ******** |
---|
11 | TITLE Undo/Redo |
---|
12 | |
---|
13 | OCCURRENCE ARB_NT ARB_EDIT4 ARB_SECEDIT |
---|
14 | |
---|
15 | DESCRIPTION The undo/redo feature works on your database. |
---|
16 | This means it will only affect actions which change the database. |
---|
17 | We cannot give you a detailed list of what affects the |
---|
18 | database (DB) and what does not - just a few examples: |
---|
19 | |
---|
20 | - changing tree or sequence data affects DB |
---|
21 | (you've guessed that!) |
---|
22 | - changing the cursor position in ARB_EDIT4 does not affect DB |
---|
23 | - changing dialogs does _sometimes_ affect DB (this depends |
---|
24 | on whether the value is save in properties or in the DB). |
---|
25 | |
---|
26 | Note that there is only _one_ undo/redo queue for all applications |
---|
27 | together, cause they all work on the same DB! |
---|
28 | If you e.g. change a tree in ARB and then change a sequence |
---|
29 | in ARB_EDIT4 you cannot undo your tree change by clicking UNDO in |
---|
30 | ARB, which would on the contrary undo your sequence change because |
---|
31 | it was your last DB-change. |
---|
32 | |
---|
33 | After undo-ing something be careful: If you change anything (that |
---|
34 | affects the DB) your current redo-list will be deleted - this |
---|
35 | means you can no longer redo your undos! |
---|
36 | |
---|
37 | NOTES The undo-depth depends on memory usage. |
---|
38 | |
---|
39 | EXAMPLES None |
---|
40 | |
---|
41 | WARNINGS None |
---|
42 | |
---|
43 | BUGS Undo crashes when "deleting a group" is undone (and in similar cases). |
---|
44 | See LINK{http://bugs.arb-home.de/ticket/496} |
---|