head	1.11;
access;
symbols
	core-8-5-9:1.10
	core-8-5-8:1.10
	macosx-cocoa-merge:1.11
	macosx-cocoa-premerge:1.11
	macosx-carbon-freeze:1.11
	core-8-5-7:1.10
	core-8-5-6:1.10
	core-8-6-b1:1.11
	core-8-6-a3:1.11
	core-8-5-5:1.10
	core-8-6-a2:1.11
	core-8-5-4:1.10
	core-8-5-3:1.10
	core-8-6-a1:1.10
	core-8-4-19:1.6
	core-8-5-branch:1.10.0.4
	core-8-5-2:1.10
	core-8-4-18:1.6
	core-8-5-1:1.10
	core-8-4-17:1.6
	core-8-5-0:1.10
	core-8-5-b3:1.10
	core-8-5-b2:1.10
	core-8-4-16:1.6
	core-8-5-b1:1.10
	core-stablilizer-merge:1.10
	core-stabilizer-branch:1.10.0.2
	core-stabilizer-merge:1.10
	core-8-4-15:1.6
	core-8-5-a6:1.10
	core-8-5-a5:1.9
	core-8-4-14:1.6
	core-8-5-a4:1.9
	core-8-4-13:1.6
	core-8-4-12:1.6
	core-8-4-11:1.6
	core-8-5-a3:1.9
	core-8-4-10:1.6
	core-8-4-9-branch:1.6.0.4
	core-8-5-a2:1.9
	core-8-4-9:1.6
	core-8-4-8:1.6
	core-8-4-7:1.6
	core-8-5-a1:1.8
	core-8-4-6:1.6
	core-8-4-5:1.6
	mistachkin-dev-branch:1.7.0.2
	core-8-4-4:1.6
	core-8-4-3:1.6
	core-8-4-branch:1.6.0.2
	core-8-4-2:1.6
	core-8-4-1:1.6
	core-8-3-5:1.3
	core-8-4-0:1.6
	macosx-8-4-merge-2002-08-31-trunk:1.6
	macosx-8-4-premerge-2002-08-31-branch:1.3.8.1
	macosx-8-4-premerge-2002-08-31-trunk:1.6
	macosx-8-4-merge-2002-08-30-branch:1.3.8.1
	macosx-8-4-merge-2002-08-30-trunk:1.6
	macosx-8-4-merge-2002-08-20-branch:1.3.8.1
	macosx-8-4-merge-2002-08-20-trunk:1.6
	core-8-4-b2:1.6
	core-8-4-b1:1.5
	macosx-premerge-6-9-02:1.3
	core-8-4-a4:1.3
	core-8-3-4:1.3
	macosx-8-4-branch:1.3.0.8
	macosx-8-4-branchpoint:1.3
	core-8-4-a3:1.3
	core-8-3-3:1.3
	dgp-privates-into-namespace:1.3.0.6
	tclpro-1-5-0:1.3
	core-8-4-win-speedup:1.3.0.4
	core-8-4-a2:1.3
	tclpro-1-4-1:1.3
	tclpro-1-4-0:1.3
	core-8-3-2:1.3
	ajuba-ajuba2-2-1-base:1.3
	ajuba-ajuba2-2-0:1.3
	core-8-4-a1:1.3
	core-8-3-1-branch:1.3.0.2
	core-8-3-1:1.3
	scriptics-sc-2-0-b5:1.3
	scriptics-sc-2-0-fixed:1.3
	scriptics-sc-2-0-b2:1.3
	scriptics-sc-2-0-b1:1.3
	core-8-3-0:1.3
	core-8-3-b2:1.3
	core-8-3-b1:1.3
	scriptics-sc-1-1:1.2
	scriptics-sc-1-1-b1:1.2
	core-8-2-3:1.2
	scriptics-sc-1-1-branch:1.2.0.16
	scriptics-sc-1-1-base:1.2
	scriptics-sc-1-0:1.2
	scriptics-sc-1-0-branch:1.2.0.14
	scriptics-sc-1-0-base:1.2
	core-8-2-2:1.2
	core-8-2-1:1.2
	scriptics-bc-1-0-b1:1.2
	core-8-2-1-branch:1.2.0.12
	scriptics-tclpro-1-3-0:1.2
	core-8-2-0:1.2
	core-8-2-b3-branch:1.2.0.10
	core-8-2-b3-base:1.2
	scriptics-tclpro-1-3-b4:1.2
	core-8-2-b2:1.2
	scriptics-tclpro-1-3-b3:1.2
	core-8-2-b1:1.2
	scriptics-tclpro-1-3-b2:1.2
	merge-to-mainline-5/21/99:1.2
	scriptics-tclpro-1-3-b2-branch:1.2.0.8
	core-8-1-1:1.2
	scriptics-tclpro-1-3-b1:1.2
	core-8-1-1-base:1.2
	core-8-1-0:1.2
	merge-to-mainline-4-29-99:1.2
	merge-to-mainline-4-23-99:1.2
	core-8-1-branch-old:1.1.0.4
	core-8-0-6-branch:1.2.0.6
	core-8-0-6-base:1.2
	core-8-0-5:1.2
	core-8-1-b3:1.1.4.1
	core-8-1-b2:1.1.4.1
	dev-8-1-stubs-branch:1.1.4.1.0.2
	dev-stubs-branch:1.2.0.4
	scriptics-tclpro-1-2:1.2
	scriptics-tclpro-1-2-b2:1.2
	core-8-1-merge-2/10/99:1.2
	core-8-0-5-branch:1.2.0.2
	core-8-0-5-base:1.2
	scriptics-tclpro-1-2-b1:1.2
	scriptics-tclpro-1-2-a1:1.2
	core-8-1-b1:1.1.4.1
	core-8-0-4:1.2
	core-8-1-a2:1.1
	core-8-0-2:1.1
	core-8-0-3:1.2;
locks; strict;
comment	@# @;


1.11
date	2008.06.30.22.57.01;	author dkf;	state Exp;
branches;
next	1.10;

1.10
date	2007.01.05.00.00.48;	author nijtmans;	state Exp;
branches;
next	1.9;

1.9
date	2004.09.19.16.05.36;	author dkf;	state Exp;
branches;
next	1.8;

1.8
date	2003.11.21.17.10.39;	author dkf;	state Exp;
branches;
next	1.7;

1.7
date	2003.03.06.15.35.51;	author dkf;	state Exp;
branches;
next	1.6;

1.6
date	2002.08.05.04.30.38;	author dgp;	state Exp;
branches;
next	1.5;

1.5
date	2002.06.14.14.07.50;	author dkf;	state Exp;
branches;
next	1.4;

1.4
date	2002.06.14.13.35.47;	author dkf;	state Exp;
branches;
next	1.3;

1.3
date	99.10.29.03.57.40;	author hobbs;	state Exp;
branches
	1.3.8.1;
next	1.2;

1.2
date	98.09.14.18.22.47;	author stanton;	state Exp;
branches;
next	1.1;

1.1
date	98.04.01.09.40.02;	author rjohnson;	state Exp;
branches
	1.1.4.1;
next	;

1.1.4.1
date	98.09.30.02.15.51;	author stanton;	state Exp;
branches;
next	;

1.3.8.1
date	2002.08.20.20.27.00;	author das;	state Exp;
branches;
next	;


desc
@@


1.11
log
@Minor doc updates (removing out of date changebars, improving typedef formatting,
 etc.)
@
text
@'\"
'\" Copyright (c) 1994 The Australian National University
'\" Copyright (c) 1994-1996 Sun Microsystems, Inc.
'\"
'\" See the file "license.terms" for information on usage and redistribution
'\" of this file, and for a DISCLAIMER OF ALL WARRANTIES.
'\" 
'\" Author: Paul Mackerras (paulus@@cs.anu.edu.au),
'\"	    Department of Computer Science,
'\"	    Australian National University.
'\"
'\" RCS: @@(#) $Id: FindPhoto.3,v 1.10 2007/01/05 00:00:48 nijtmans Exp $
'\"
.so man.macros
.TH Tk_FindPhoto 3 8.0 Tk "Tk Library Procedures"
.BS
.SH NAME
Tk_FindPhoto, Tk_PhotoPutBlock, Tk_PhotoPutZoomedBlock, Tk_PhotoGetImage, Tk_PhotoBlank, Tk_PhotoExpand, Tk_PhotoGetSize, Tk_PhotoSetSize \- manipulate the image data stored in a photo image.
.SH SYNOPSIS
.nf
\fB#include <tk.h>\fR
.sp
Tk_PhotoHandle
\fBTk_FindPhoto\fR(\fIinterp, imageName\fR)
.sp
int
\fBTk_PhotoPutBlock\fR(\fIinterp, handle, blockPtr, x, y, width, height,\
compRule\fR)
.sp
int
\fBTk_PhotoPutZoomedBlock\fR(\fIinterp, handle, blockPtr, x, y, width, height,\
zoomX, zoomY, subsampleX, subsampleY, compRule\fR)
.sp
int
\fBTk_PhotoGetImage\fR(\fIhandle, blockPtr\fR)
.sp
void
\fBTk_PhotoBlank\fR(\fIhandle\fR)
.sp
int
\fBTk_PhotoExpand\fR(\fIinterp, handle, width, height\fR)
.sp
void
\fBTk_PhotoGetSize\fR(\fIhandle, widthPtr, heightPtr\fR)
.sp
int
\fBTk_PhotoSetSize\fR(\fIinterp. handle, width, height\fR)
.SH ARGUMENTS
.AS Tk_PhotoImageBlock window_path
.AP Tcl_Interp *interp in
Interpreter in which image was created and in which error reporting is
to be done.
.AP "const char" *imageName in
Name of the photo image.
.AP Tk_PhotoHandle handle in
Opaque handle identifying the photo image to be affected.
.AP Tk_PhotoImageBlock *blockPtr in
Specifies the address and storage layout of image data.
.AP int x in
Specifies the X coordinate where the top-left corner of the block is
to be placed within the image.
.AP int y in
Specifies the Y coordinate where the top-left corner of the block is
to be placed within the image.
.AP int width in
Specifies the width of the image area to be affected (for
\fBTk_PhotoPutBlock\fR) or the desired image width (for
\fBTk_PhotoExpand\fR and \fBTk_PhotoSetSize\fR).
.AP int compRule in
Specifies the compositing rule used when combining transparent pixels
in a block of data with a photo image.  Must be one of
\fBTK_PHOTO_COMPOSITE_OVERLAY\fR (which puts the block of data over the top
of the existing photo image, with the previous contents showing
through in the transparent bits) or \fBTK_PHOTO_COMPOSITE_SET\fR (which
discards the existing photo image contents in the rectangle covered by
the data block.)
.AP int height in
Specifies the height of the image area to be affected (for
\fBTk_PhotoPutBlock\fR) or the desired image height (for
\fBTk_PhotoExpand\fR and \fBTk_PhotoSetSize\fR).
.AP int *widthPtr out
Pointer to location in which to store the image width.
.AP int *heightPtr out
Pointer to location in which to store the image height.
.AP int subsampleX in
Specifies the subsampling factor in the X direction for input
image data.
.AP int subsampleY in
Specifies the subsampling factor in the Y direction for input
image data.
.AP int zoomX in
Specifies the zoom factor to be applied in the X direction to pixels
being written to the photo image.
.AP int zoomY in
Specifies the zoom factor to be applied in the Y direction to pixels
being written to the photo image.
.BE
.SH DESCRIPTION
.PP
\fBTk_FindPhoto\fR returns an opaque handle that is used to identify a
particular photo image to the other procedures.  The parameter is the
name of the image, that is, the name specified to the \fBimage create
photo\fR command, or assigned by that command if no name was specified.
.PP
\fBTk_PhotoPutBlock\fR is used to supply blocks of image data to be
displayed.  The call affects an area of the image of size
\fIwidth\fR x \fIheight\fR pixels, with its top-left corner at
coordinates (\fIx\fR,\fIy\fR).  All of \fIwidth\fR, \fIheight\fR,
\fIx\fR, and \fIy\fR must be non-negative.
If part of this area lies outside the
current bounds of the image, the image will be expanded to include the
area, unless the user has specified an explicit image size with the
\fB\-width\fR and/or \fB\-height\fR widget configuration options
(see photo(n)); in that
case the area is silently clipped to the image boundaries.
.PP
The \fIblock\fR parameter is a pointer to a
\fBTk_PhotoImageBlock\fR structure, defined as follows:
.CS
typedef struct {
    unsigned char *\fIpixelPtr\fR;
    int \fIwidth\fR;
    int \fIheight\fR;
    int \fIpitch\fR;
    int \fIpixelSize\fR;
    int \fIoffset\fR[4];
} \fBTk_PhotoImageBlock\fR;
.CE
The \fIpixelPtr\fR field points to the first pixel, that is, the
top-left pixel in the block.
The \fIwidth\fR and \fIheight\fR fields specify the dimensions of the
block of pixels.  The \fIpixelSize\fR field specifies the address
difference between two horizontally adjacent pixels.  Often it is 3
or 4, but it can have any value.  The \fIpitch\fR field specifies the
address difference between two vertically adjacent pixels.  The
\fIoffset\fR array contains the offsets from the address of a pixel
to the addresses of the bytes containing the red, green, blue and alpha
(transparency) components.  These are normally 0, 1, 2 and 3, but can
have other values, e.g., for images that are stored as separate red,
green and blue planes.
.PP
The \fIcompRule\fR parameter to \fBTk_PhotoPutBlock\fR specifies a
compositing rule that says what to do with transparent pixels.  The
value \fBTK_PHOTO_COMPOSITE_OVERLAY\fR says that the previous contents of
the photo image should show through, and the value
\fBTK_PHOTO_COMPOSITE_SET\fR says that the previous contents of the photo
image should be completely ignored, and the values from the block be
copied directly across.  The behavior in Tk8.3 and earlier was
equivalent to having \fBTK_PHOTO_COMPOSITE_OVERLAY\fR as a compositing rule.
.PP
The value given for the \fIwidth\fR and \fIheight\fR parameters to
\fBTk_PhotoPutBlock\fR do not have to correspond to the values specified
in \fIblock\fR.  If they are smaller, \fBTk_PhotoPutBlock\fR extracts a
sub-block from the image data supplied.  If they are larger, the data
given are replicated (in a tiled fashion) to fill the specified area.
These rules operate independently in the horizontal and vertical
directions.
.PP
\fBTk_PhotoPutBlock\fR normally returns \fBTCL_OK\fR, though if it cannot
allocate sufficient memory to hold the resulting image, \fBTCL_ERROR\fR is
returned instead and, if the \fIinterp\fR argument is non-NULL, an
error message is placed in the interpreter's result.
.PP
\fBTk_PhotoPutZoomedBlock\fR works like \fBTk_PhotoPutBlock\fR except that
the image can be reduced or enlarged for display.  The
\fIsubsampleX\fR and \fIsubsampleY\fR parameters allow the size of the
image to be reduced by subsampling.
\fBTk_PhotoPutZoomedBlock\fR will use only pixels from the input image
whose X coordinates are multiples of \fIsubsampleX\fR, and whose Y
coordinates are multiples of \fIsubsampleY\fR.  For example, an image
of 512x512 pixels can be reduced to 256x256 by setting
\fIsubsampleX\fR and \fIsubsampleY\fR to 2.
.PP
The \fIzoomX\fR and \fIzoomY\fR parameters allow the image to be
enlarged by pixel replication.  Each pixel of the (possibly subsampled)
input image will be written to a block \fIzoomX\fR pixels wide and
\fIzoomY\fR pixels high of the displayed image.  Subsampling and
zooming can be used together for special effects.
.PP
\fBTk_PhotoGetImage\fR can be used to retrieve image data from a photo
image.  \fBTk_PhotoGetImage\fR fills
in the structure pointed to by the \fIblockPtr\fR parameter with values
that describe the address and layout of the image data that the
photo image has stored internally.  The values are valid
until the image is destroyed or its size is changed.
\fBTk_PhotoGetImage\fR returns 1 for compatibility with the
corresponding procedure in the old photo widget.
.PP
\fBTk_PhotoBlank\fR blanks the entire area of the
photo image.  Blank areas of a photo image are transparent.
.PP
\fBTk_PhotoExpand\fR requests that the widget's image be expanded to be
at least \fIwidth\fR x \fIheight\fR pixels in size.  The width and/or
height are unchanged if the user has specified an explicit image width
or height with the \fB\-width\fR and/or \fB\-height\fR configuration
options, respectively.
If the image data
are being supplied in many small blocks, it is more efficient to use
\fBTk_PhotoExpand\fR or \fBTk_PhotoSetSize\fR at the beginning rather than
allowing the image to expand in many small increments as image blocks
are supplied.
.PP
\fBTk_PhotoExpand\fR normally returns \fBTCL_OK\fR, though if it cannot
allocate sufficient memory to hold the resulting image, \fBTCL_ERROR\fR is
returned instead and, if the \fIinterp\fR argument is non-NULL, an
error message is placed in the interpreter's result.
.PP
\fBTk_PhotoSetSize\fR specifies the size of the image, as if the user
had specified the given \fIwidth\fR and \fIheight\fR values to the
\fB\-width\fR and \fB\-height\fR configuration options.  A value of
zero for \fIwidth\fR or \fIheight\fR does not change the image's width
or height, but allows the width or height to be changed by subsequent
calls to \fBTk_PhotoPutBlock\fR, \fBTk_PhotoPutZoomedBlock\fR or
\fBTk_PhotoExpand\fR.
.PP
\fBTk_PhotoSetSize\fR normally returns \fBTCL_OK\fR, though if it cannot
allocate sufficient memory to hold the resulting image, \fBTCL_ERROR\fR is
returned instead and, if the \fIinterp\fR argument is non-NULL, an
error message is placed in the interpreter's result.
.PP
\fBTk_PhotoGetSize\fR returns the dimensions of the image in
*\fIwidthPtr\fR and *\fIheightPtr\fR.
.SH PORTABILITY
.PP
In Tk 8.3 and earlier, \fBTk_PhotoPutBlock\fR and
\fBTk_PhotoPutZoomedBlock\fR had different signatures. If you want to
compile code that uses the old interface against 8.4 without updating
your code, compile it with the flag
-DUSE_COMPOSITELESS_PHOTO_PUT_BLOCK.  Code linked using Stubs against
older versions of Tk will continue to work.
.PP
In Tk 8.4, \fBTk_PhotoPutBlock\fR, \fBTk_PhotoPutZoomedBlock\fR,
\fBTk_PhotoExpand\fR and \fBTk_PhotoSetSize\fR did not take an
\fIinterp\fR argument or return any result code.  If insufficient
memory was available for an image, Tk would panic.  This behaviour is
still supported if you compile your extension with the additional flag
-DUSE_PANIC_ON_PHOTO_ALLOC_FAILURE.  Code linked using Stubs against
older versions of Tk will continue to work.
.SH CREDITS
.PP
The code for the photo image type was developed by Paul Mackerras,
based on his earlier photo widget code.
.SH KEYWORDS
photo, image
@


1.10
log
@various "const" additions, in line with TIP #27
fix bug #1627732
@
text
@d12 1
a12 1
'\" RCS: @@(#) $Id: FindPhoto.3,v 1.9 2004/09/19 16:05:36 dkf Exp $
a25 1
.VS 8.5
a32 1
.VE 8.5
a39 1
.VS 8.5
a41 1
.VE 8.5
a45 1
.VS 8.5
a47 1
.VE 8.5
a97 1

d126 2
a127 2
    int \fIoffset[4]\fR;
} Tk_PhotoImageBlock;
a158 1
.VS 8.5
a162 1
.VE 8.5
a202 1
.VS 8.5
a206 1
.VE 8.5
a215 1
.VS 8.5
a219 1
.VE 8.5
a222 1

a231 1
.VS 8.5
a238 2
.VE 8.5

a242 1

@


1.9
log
@Standardize style of section refs & public symbols. Remove displayed tabs
@
text
@d12 1
a12 1
'\" RCS: @@(#) $Id: FindPhoto.3,v 1.8 2003/11/21 17:10:39 dkf Exp $
d59 1
a59 1
.AP "CONST char" *imageName in
@


1.8
log
@Thanks to davidw for spotting a reference to a header that's not been around
for many years now...
@
text
@d12 1
a12 1
'\" RCS: @@(#) $Id: FindPhoto.3,v 1.7 2003/03/06 15:35:51 dkf Exp $
d78 1
a78 1
TK_PHOTO_COMPOSITE_OVERLAY (which puts the block of data over the top
d80 1
a80 1
through in the transparent bits) or TK_PHOTO_COMPOSITE_SET (which
d128 6
a133 6
	unsigned char *\fIpixelPtr\fR;
	int \fIwidth\fR;
	int \fIheight\fR;
	int \fIpitch\fR;
	int \fIpixelSize\fR;
	int \fIoffset[4]\fR;
d151 1
a151 1
value TK_PHOTO_COMPOSITE_OVERLAY says that the previous contents of
d153 1
a153 1
TK_PHOTO_COMPOSITE_SET says that the previous contents of the photo
d156 1
a156 1
equivalent to having TK_PHOTO_COMPOSITE_OVERLAY as a compositing rule.
d167 2
a168 2
\fBTk_PhotoPutBlock\fR normally returns TCL_OK, though if it cannot
allocate sufficient memory to hold the resulting image, TCL_ERROR is
d213 2
a214 2
\fBTk_PhotoExpand\fR normally returns TCL_OK, though if it cannot
allocate sufficient memory to hold the resulting image, TCL_ERROR is
d228 2
a229 2
\fBTk_PhotoSetSize\fR normally returns TCL_OK, though if it cannot
allocate sufficient memory to hold the resulting image, TCL_ERROR is
@


1.7
log
@Documentation changes due to TIP#116
@
text
@d12 1
a12 1
'\" RCS: @@(#) $Id: FindPhoto.3,v 1.6 2002/08/05 04:30:38 dgp Exp $
a21 1
\fB#include <tkPhoto.h>\fR
@


1.6
log
@Applied companion patch for Tcl Patch 585105,
updating Tk to use Tcl 8.4's fully CONST-ified
interface, and fully CONSTifying Tk at the
same time.

This patch includes purging Tk of its last
direct access to interp->result.  [Bug 589853]

The substantial changes include copying
event sequence strings into Tcl_DStrings
in tkBind.c, and copying [text] indices into
Tcl_DStrings because parsing them involved
overwriting them.  If this causes performance
trouble, that can be resolved by further
converting them to Tcl_Obj's.

The #defines USE_NON_CONST and USE_COMPAT_CONST
have the same effect for Tk as they do for Tcl.
(They actually change tcl.h)
@
text
@d12 1
a12 1
'\" RCS: @@(#) $Id: FindPhoto.3,v 1.5 2002/06/14 14:07:50 dkf Exp $
a24 1
.VS 8.0 br
a25 1
.VE
d27 4
a30 2
void
\fBTk_PhotoPutBlock\fR(\fIhandle, blockPtr, x, y, width, height, compRule\fR)
d32 2
a33 2
void
\fBTk_PhotoPutZoomedBlock\fR(\fIhandle, blockPtr, x, y, width, height,\
d35 1
d43 4
a46 2
void
\fBTk_PhotoExpand\fR(\fIhandle, width, height\fR)
d51 4
a54 2
void
\fBTk_PhotoSetSize\fR(\fIhandle, width, height\fR)
d58 2
a59 3
.VS
Interpreter in which image was created.
.VE
a75 1
.VS 8.4
a83 1
.VE 8.4
a149 1
.VS 8.4
a157 1
.VE 8.4
d167 7
d213 7
d228 7
a238 1
.VS 8.4
d246 10
a255 1
.VE 8.4
@


1.5
log
@Changed some _Old and _OLD to more descriptive terms.
@
text
@d12 1
a12 1
'\" RCS: @@(#) $Id: FindPhoto.3,v 1.4 2002/06/14 13:35:47 dkf Exp $
d56 1
a56 1
.AP char *imageName in
@


1.4
log
@TIP#98 implementation; improved photo image copy and GIF frame access
@
text
@d12 1
a12 1
'\" RCS: @@(#) $Id: FindPhoto.3,v 1.3 1999/10/29 03:57:40 hobbs Exp $
d223 3
a225 2
your code, compile it with the flag -DUSE_OLD_PHOTO_PUT_BLOCK.  Code
linked using Stubs against older versions of Tk will continue to work.
@


1.3
log
@	* doc/CrtImgType.3:
	* doc/CrtPhImgFmt.3:
	* doc/FindPhoto.3:
	* doc/photo.n: new docs for Img patch mods
@
text
@d12 1
a12 1
'\" RCS: @@(#) $Id: FindPhoto.3,v 1.2 1998/09/14 18:22:47 stanton Exp $
d30 1
a30 1
\fBTk_PhotoPutBlock\fR(\fIhandle, blockPtr, x, y, width, height\fR)
d34 1
a34 1
zoomX, zoomY, subsampleX, subsampleY\fR)
d72 10
d148 11
d216 10
@


1.3.8.1
log
@merged with trunk at tag macosx-8-4-merge-2002-08-20-trunk
@
text
@d12 1
a12 1
'\" RCS: @@(#) $Id$
d30 1
a30 1
\fBTk_PhotoPutBlock\fR(\fIhandle, blockPtr, x, y, width, height, compRule\fR)
d34 1
a34 1
zoomX, zoomY, subsampleX, subsampleY, compRule\fR)
d56 1
a56 1
.AP "CONST char" *imageName in
a71 10
.VS 8.4
.AP int compRule in
Specifies the compositing rule used when combining transparent pixels
in a block of data with a photo image.  Must be one of
TK_PHOTO_COMPOSITE_OVERLAY (which puts the block of data over the top
of the existing photo image, with the previous contents showing
through in the transparent bits) or TK_PHOTO_COMPOSITE_SET (which
discards the existing photo image contents in the rectangle covered by
the data block.)
.VE 8.4
a137 11
.VS 8.4
The \fIcompRule\fR parameter to \fBTk_PhotoPutBlock\fR specifies a
compositing rule that says what to do with transparent pixels.  The
value TK_PHOTO_COMPOSITE_OVERLAY says that the previous contents of
the photo image should show through, and the value
TK_PHOTO_COMPOSITE_SET says that the previous contents of the photo
image should be completely ignored, and the values from the block be
copied directly across.  The behavior in Tk8.3 and earlier was
equivalent to having TK_PHOTO_COMPOSITE_OVERLAY as a compositing rule.
.VE 8.4
.PP
a194 11

.SH PORTABILITY
.VS 8.4
.PP
In Tk 8.3 and earlier, \fBTk_PhotoPutBlock\fR and
\fBTk_PhotoPutZoomedBlock\fR had different signatures. If you want to
compile code that uses the old interface against 8.4 without updating
your code, compile it with the flag
-DUSE_COMPOSITELESS_PHOTO_PUT_BLOCK.  Code linked using Stubs against
older versions of Tk will continue to work.
.VE 8.4
@


1.2
log
@Replaced SCCS strings, fixed binary files
@
text
@d12 1
a12 1
'\" RCS: @@(#) $Id$
d122 1
a122 1
	int \fIoffset[3]\fR;
d133 4
a136 4
to the addresses of the bytes containing the red, green and blue
components.  These are normally 0, 1 and 2, but can have other values,
e.g., for images that are stored as separate red, green and blue
planes.
@


1.1
log
@Initial revision
@
text
@d12 1
a12 1
'\" "@@(#) FindPhoto.3 1.11 97/08/22 18:52:33"
@


1.1.4.1
log
@Merged 8.0.3 changes into 8.1
@
text
@d12 1
a12 1
'\" RCS: @@(#) $Id: FindPhoto.3,v 1.2 1998/09/14 18:22:47 stanton Exp $
@


