[interfacekit] Re: BPicture

It seems to be 0x202, data size seems to be always 16. At the end there's a
BPoint(8) and the clip_to_inverse_picture bool(1), which leaves 7 bytes. So
where's the picture to clip to? Those 7 bytes are all 0 btw. There is also
nothing extra stored in the picture data.

Marc Flerackers (mflerackers@xxxxxxxxxx)
Software Engineer
ANDROME NV

> -----Original Message-----
> From: interfacekit-bounce@xxxxxxxxxxxxx
> [mailto:interfacekit-bounce@xxxxxxxxxxxxx]On Behalf Of Philippe Houdoin
> Sent: woensdag 25 september 2002 8:39
> To: interfacekit@xxxxxxxxxxxxx
> Subject: [interfacekit] Re: BPicture
>
>
>
>
> >I checked it in under /current/docs/develop/interface.  Great document
> >Marc; you've been doing some serious poking about with the debugger,
> >haven't you=3F ;)
>
> Agreed too myself.
>
> Give a looke at some undocumented BPicture iteration handlers we (PDF
> Writer team) have discover
> during driver development:
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/open-beos/current/src/
> add-ons/print/drivers/pdf/source/PictureIterator.cpp=3Frev=3D1.1&content-
> type=3Dtext/vnd.viewcvs-markup
>
> I will bet that a ClipToPicture instruction would be there, maybe
> behind 0x0202, in place of 0x0205...
>
> -Philippe
>
> --
> Fortune Cookie Says:
>
> "To vacillate or not to vacillate, that is the question ... or is it?"
>
>

Other related posts: