/[gzz]/gzz/doc/pegboard/1009/PEG_1009.rst
ViewVC logotype

Diff of /gzz/doc/pegboard/1009/PEG_1009.rst

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.12 by benja, Mon Oct 7 04:33:07 2002 UTC revision 1.13 by tjl, Mon Oct 7 05:09:55 2002 UTC
# Line 25  Add into VobCoorder the following conven Line 25  Add into VobCoorder the following conven
25          return ortho(into, 0, 0, 0, x, y);          return ortho(into, 0, 0, 0, x, y);
26      }      }
27    
28  and rename coordsys into ortho  and rename coordsys into ortho.
   
   
     (Benja says:) ``scale`` doesn't belong here, because AWT cannot do it properly  
     when text is involved (because text's aspect ratio may change  
     with size).    
           
         (Tjl:) Well, coordsys already *does* scale. The thing is to just  
         ask for the font's width with the right scale, which you should  
         be able to ask the coordsys. Something like ::  
   
             scale = vs.getHeight(cs);  
   
         ?  
           
             (Benja:) We have talked about this earlier. It messes up the  
             layout, because *the aspect ratio changes*, as I have said above.  
             You *cannot* assume that you can scale below the view level in AWT.  
   
                 (Tjl:) I didn't make my point clear. We *can* do this,  
                 if we ask, at vobscene construction time,  
                 how tall a given cs will be.  
                   
                     (Benja:) Ah. Now I understand somewhat... However,  
                     even then, you cannot satisfy scaling in two dimensions,  
                     so it would have to be ``scale(int into, float scale)``.  
                     Also, you're talking about the "height" of a coordsys--  
                     what is this? Coordsys are, at this point, transformations  
                     of points-- so what's the "height" of a transformation?  
                     Finally, I still don't like scale being here, because  
                     generally having to know the scale before the view  
                     comes in means that we cannot switch to a system where  
                     (in gl) we determine the parent transformations  
                     *after* the views have done their job. For example in  
                     text layout, it would be nice if we could first render  
                     the text with a given width, then look at the resulting  
                     height and decide how to translate the result-- this  
                     requires that a coordsys gets its parent after it  
                     is first created-- not currently allowed, but not  
                     impossible to change.  
                       
29    
30  And into AffineVobCoorder the following functions::  And into AffineVobCoorder the following functions::
31    

Legend:
Removed from v.1.12  
changed lines
  Added in v.1.13

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26