[interfacekit] Re: BPicture
- From: "Philippe Houdoin" <philippe.houdoin@xxxxxxx>
- To: interfacekit@xxxxxxxxxxxxx
- Date: Wed, 25 Sep 2002 08:38:50 +0200 (added by postmaster@wanadoo.fr)
>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?"
- Follow-Ups:
- [interfacekit] Re: BPicture
- From: Marc Flerackers
Other related posts:
- » [interfacekit] BPicture
- » [interfacekit] Re: BPicture
- » [interfacekit] Re: BPicture
- » [interfacekit] Re: BPicture
- » [interfacekit] Re: BPicture
- » [interfacekit] Re: BPicture
- » [interfacekit] BPicture
- » [interfacekit] Re: BPicture
- » [interfacekit] Re: BPicture
- » [interfacekit] Re: BPicture
- » [interfacekit] Re: BPicture
- » [interfacekit] Re: BPicture
- [interfacekit] Re: BPicture
- From: Marc Flerackers