[Kst] kdeextragear-2/kst/devel-docs

[George Staikos]

CVS commit by staikos: 

some more details


  M +27 -3     updates.txt   1.4


--- kdeextragear-2/kst/devel-docs/updates.txt  #1.3:1.4
@@ -5,12 +5,36 @@
 
 - update() is implemented in view objects
+    view objects form a tree already, so update() should propagate through the
+    view object tree.  Most will do little more than update their children.
+    Plots, most importantly, will trigger the updates of curves which will
+    trigger the updates of data objects and data sources.  
+    update() does not -paint- anything.  No pixmaps are touched here!
+
 - locking is implemented in view objects
+    The implementation of update() will require the implementation of locking
+    since their members will be accessible in >1 thread.
+
 - dirty flag is implemented in kstobjects to indicate if an update should
-  happen despite no new data and no dependents with updates
+  happen despite no new data and no dependents with updates.  This will be used
+  to determine if updates should happen due to property changes in objects.
+  (ex: curve changes colour)
+
 - update thread now only updates [visible] view objects, and then rvectors
    - updates propagate downward to update dependent objects
-          -> more efficient
+          -> more efficient, no repainting of unnecessary objects
+   - updating rvectors allows us to keep data current.
+
 - scalars become first class citizens
+   - Scalars and strings can make objects do updates now.  This is needed
+   because some objects (such as plugins) can depend on the output of another
+   object where that output is a scalar.  Right now these updates don't work
+   properly.
+
 - updates store the "last result" and send that if the current counter has already been encountered (fixes some bugs)
+   if (checkUpdateCounter(counter)) {
+           return _lastUpdateResult;
+   }
+   
 - threading and painting stay as they are
-
+   - We won't add more threads yet but hope to do so in the future.
+   - Painting continues to work as it does.  There is no reason to move it.