Changes between Version 9 and Version 10 of TEXT_LAYOUT_LAZY

Timestamp:

02/14/10 12:50:58 (15 years ago)

Author:

kyli

Comment:

--

TEXT_LAYOUT_LAZY

@@ -81 +81 @@
   * Otherwise, calls update() to the last layout.
 
-Obviously, in general, the text flow makes INVALID layouts PARTIALLY_VALID ones, and the aut-chaining invalidates VALID ones. So, we need someone to completely validate PARTIALLY_VALID layouts. Here comes the 
+Obviously, in general, the text flow makes INVALID layouts PARTIALLY_VALID ones, and the auto-chaining invalidates VALID ones. So, we need someone to completely validate PARTIALLY_VALID layouts. Here comes the 
 
- * '''Background thread'''.
+ * '''Background thread'''. This should be a daemon thread, which runs with lowest priority and the only thing it does is
+  * If the current layout is PARTIALLY_VALID, calls its ''validateNextArea()'' method with the current text and areas. The result is saved to a RwProp ''backgroundLayout()'' in the text flow. 
+ This result should somehow be used, so we add a new rule:
+  * The text flow tracks the background layout and if it is not INVALID with the current text and areas, uses it instead of the last computed layout.
+
+After a number of iterations, the background thread will completely validate the layout, which means that the auto-chaining will still work, it will just be delayed in time.