On Mon, 24 Apr 2000, Jon M. Taylor wrote:
> On Sat, 22 Apr 2000, Rodolphe Ortalo wrote:
> >
> > Is it possible to have several miPaintedSet per ggi_visual_t ?
>
> Sure, in fact miPaintedSets are not tied to any one ggi_visual at
> present, although this may change in the future (see below).
Hmm... Okay. But then, in LiXMI API, most functions take two
parameters: the ggi_visual_t AND the miPaintedSet
(or the ggi_visual_t and the miGC - or miCanvas).
Would it be possible to clean up the API and use only a single object ?
>From what I understand of XMI, and of your future plans, it seems to me
that 'drawing functions' should operate over a paintedSet in fact, no ?
Can't you get rid of the ggi_visual_t then, except for the
miCopyPaintedSetToCanvas ?
Well, I don't really mind in fact -- but the question rose in my mind
while I was wrapping up the LibXMI functions in LibGWT: I wondered if it
was really needed to do repeatedly things like:
void gwtmiDrawPoints(gwt_window_t win, miPaintedSet *paintedSet,
const miGC *pGC, miCoordMode mode,
int npts, const miPoint *pPts)
{
miDrawPoints(win->visual, paintedSet, pGC, mode, npts, pPts);
}
Only gwtmiCopyPaintedSetToCanvas actually required some 'real' work
(ie: clipping to the window visible region rectangles). Note that I don't
mind at all to do 'unreal' work: 'tis pretty easy... :-)
Just my 0.02
Rodolphe
BTW: I have a polygon in a window now :-)
