Kaydet (Commit) be3dc27f authored tarafından Bjoern Michaelsen's avatar Bjoern Michaelsen

update docs

Change-Id: I94ceaafd34caba48965ee58c1fcd9a88bce416f8
üst 2c47eb3d
...@@ -51,14 +51,11 @@ class SfxHint; ...@@ -51,14 +51,11 @@ class SfxHint;
SwClient objects. The SwDepend class allows to handle their notifications in the same SwClient objects. The SwDepend class allows to handle their notifications in the same
notification callback as it forwards the Modify() calls it receives to a "master" notification callback as it forwards the Modify() calls it receives to a "master"
SwClient implementation. SwClient implementation.
The SwClientIter class allows to iterate over the SwClient objects registered at an The SwIterator class allows to iterate over the SwClient objects registered at an
SwModify. For historical reasons its ability to use TypeInfo to restrict this iteration SwModify. For historical reasons its ability to use TypeInfo to restrict this iteration
to objects of a particular type created a lot of code that misuses SwClient-SwModify to objects of a particular type created a lot of code that misuses SwClient-SwModify
relationships that basically should be used only for Modify() callbacks. relationships that basically should be used only for Modify/Notify callbacks.
This is still subject to refactoring. This is still subject to refactoring.
Until this gets resolved, new SwClientIter base code should be reduced to the absolute
minimum and it also should be wrapped by SwIterator templates that prevent that the
code gets polluted by pointer casts (see switerator.hxx).
*/ */
class SwModify; class SwModify;
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment