[Gzz-commits] gzz/doc/pegboard/1013 PEG_1013.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Benja Fallenstein <address@hidden>      02/11/21 18:39:26

Modified files:
        doc/pegboard/1013: PEG_1013.rst 

Log message:
        Make clipping PEG current-- needed now

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/doc/pegboard/1013/PEG_1013.rst.diff?tr1=1.2&tr2=1.3&r1=text&r2=text

Patches:
Index: gzz/doc/pegboard/1013/PEG_1013.rst
diff -u gzz/doc/pegboard/1013/PEG_1013.rst:1.2 
gzz/doc/pegboard/1013/PEG_1013.rst:1.3
--- gzz/doc/pegboard/1013/PEG_1013.rst:1.2      Thu Nov 14 10:40:06 2002
+++ gzz/doc/pegboard/1013/PEG_1013.rst  Thu Nov 21 18:39:26 2002
@@ -2,10 +2,10 @@
 PEG 1013: Add clipping state to vob scenes
 =============================================================
 
-:Author:   Benja Fallenstein
-:Last-Modified: $Date: 2002/11/14 15:40:06 $
-:Revision: $Revision: 1.2 $
-:Status:   Incomplete
+:Author:       Benja Fallenstein
+:Last-Modified: $Date: 2002/11/21 23:39:26 $
+:Revision:     $Revision: 1.3 $
+:Status:       Current
 
 
 Currently there is no way to clip vobs independent of the
@@ -17,6 +17,8 @@
 the given clip, then removes the clipping state and returns.
 In AWT, clipping is currently unhandled.
 
+This is needed for alpha4 in order to fix the AWT client.
+
 
 Changes
 -------
@@ -36,7 +38,7 @@
      *  specify the semantics of this method, and is not required
      *  to be implemented through a stack data structure.
      */
-    void clipRect(int cs, float x, float y, float w, float h);
+    void clipRect(int cs, float x, float y, float sx, float sh);
     
     /** Pop the topmost clipping area off the stack.
      *  The last pushed clipping area is popped off the stack and
@@ -64,10 +66,15 @@
 for being used as a stack).
 
 
-Open issues
------------
+Issues
+------
 
-How are the new ``VobScene`` methods implemented? Will there be
-``GraphicsAPI``-specific subclasses, or will the calls be passed
-to ``VobCoorder``, which has ``GraphicsAPI``-dependent
-implementations currently?
+- How are the new ``VobScene`` methods implemented? Will there be
+  ``GraphicsAPI``-specific subclasses, or will the calls be passed
+  to ``VobCoorder``, which has ``GraphicsAPI``-dependent
+  implementations currently?
+
+  RESOLVED: They will be directed to ``VobCoorder``, since this
+  results in less changes to the architecture. There will be
+  ``clipRect()`` and ``unclip()`` methods with the same signature
+  in ``VobCoorder``.