diff options
| author | Campbell Barton <ideasman42@gmail.com> | 2020-10-02 02:48:41 +0300 |
|---|---|---|
| committer | Campbell Barton <ideasman42@gmail.com> | 2020-10-02 04:59:16 +0300 |
| commit | 28ebe827e60c84ed4731a9f8aa701ccf2d8be0b0 (patch) | |
| tree | 564016446a394c3ec547dd0c250057cec7ecd61d /doc/python_api/rst/info_gotcha.rst | |
| parent | e2e31b9baca8fa98273f029c6ca47eab662db747 (diff) | |
Cleanup: trailing space
Diffstat (limited to 'doc/python_api/rst/info_gotcha.rst')
| -rw-r--r-- | doc/python_api/rst/info_gotcha.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/python_api/rst/info_gotcha.rst b/doc/python_api/rst/info_gotcha.rst index eb5cc143a2c..e5ff56063b5 100644 --- a/doc/python_api/rst/info_gotcha.rst +++ b/doc/python_api/rst/info_gotcha.rst @@ -677,7 +677,7 @@ Here are some general hints to avoid running into these problems: Undo/Redo --------- -For safety, you should assume that undo and redo always invalidates all :class:`bpy.types.ID` +For safety, you should assume that undo and redo always invalidates all :class:`bpy.types.ID` instances (Object, Scene, Mesh, Light, etc.), as weel obviously as all of their sub-data. This example shows how you can tell undo changes the memory locations: @@ -701,7 +701,7 @@ interactively by the user is the only way to make sure that the script doesn't b Modern undo/redo system does not systematically invalidate all pointers anymore. Some data (in fact, most data, in typical cases), which were detected as unchanged for a particular history step, may remain unchanged and hence their pointers may remain valid. - + Be aware that if you want to take advantage of this behavior for some reason, there is no guarantee of any kind that it will be safe and consistent. Use it at your own risk. |