Path: utzoo!utgpu!water!watmath!clyde!bellcore!tness7!tness1!sugar!peter From: peter@sugar.UUCP (Peter da Silva) Newsgroups: comp.sys.amiga.tech Subject: Re: Cookie Cut BltBitMap Keywords: function needed Message-ID: <2243@sugar.UUCP> Date: 3 Jul 88 12:28:52 GMT References: <406@icus.UUCP> <58733@sun.uucp> <2238@sugar.UUCP> <4177@cbmvax.UUCP> Organization: Sugar Land UNIX - Houston, TX Lines: 33 In article <4177@cbmvax.UUCP>, jesup@cbmvax.UUCP (Randell Jesup) writes: > >Why isn't there a general Blt function? > > Blt(src1, src1x, src1y, src2, src2x, src2y, src3, src3x, src3y, > > destrp, destx, desty, sizex, sizey, minterm); > I'd love such a function too. Unfortunately, for certain cases > arbitrary rectangle operations require the A source for a mask. Tom can > explain it better than I. I think the killer is when the sources must be > shifted in different directions, or when the byte counts are wrong, or some > such; and the FWM/LWM don't always hit the right word. OK, how about this one: Blt(src1, src2, src3, src3x, src3y, destrp, destx, desty, sizex, sizey, minterm); Since most of the time when you do this src1 and src2 are going to be blitted in in their entirety... src1==object, src2==mask, src3==image. Often src3 and dest are the same thing. I'm sure that the BoB routines must have some sort of cookie-cutter blit-in function. I couldn't find one in the manuals. How about providing an entry point for that? BltObject(object, mask, destrp, x, y, sizex, sizey); The set of library routines for doing Blits seems pretty incomplete. Maybe we need a blit.library??? Does BlitLab go through the layers library? -- -- `-_-' Peter (have you hugged your wolf today?) da Silva. -- U Mail to ...!uunet!sugar!peter, flames to /dev/null. -- "Running DOS on a '386 is like driving an Indy car to the Stop-N-Go"