PS_OPEN_IMAGE(3) 1 PS_OPEN_IMAGE(3)ps_open_image - Reads an image for later placementSYNOPSIS
int ps_open_image (resource $psdoc, string $type, string $source, string $data, int $lenght, int $width, int $height, int $compo-
nents, int $bpc, string $params)
DESCRIPTION
Reads an image which is already available in memory. The parameter $source is currently not evaluated and assumed to be memory. The image
data is a sequence of pixels starting in th upper left corner and ending in the lower right corner. Each pixel consists of $components
color components, and each component has $bpc bits.
PARAMETERS
o $psdoc
- Resource identifier of the postscript file as returned by ps_new(3).
o $type
- The type of the image. Possible values are png, jpeg, or eps.
o $source
- Not used.
o $data
- The image data.
o $length
- The length of the image data.
o $width
- The width of the image.
o $height
- The height of the image.
o $components
- The number of components for each pixel. This can be 1 (gray scale images), 3 (rgb images), or 4 (cmyk, rgba images).
o $bpc
- Number of bits per component (quite often 8).
o $params
-
RETURN VALUES
Returns identifier of image or zero in case of an error. The identifier is a positive number greater than 0.
SEE ALSO ps_open_image_file(3), ps_place_image(3), ps_close_image(3).
PHP Documentation Group PS_OPEN_IMAGE(3)
Check Out this Related Man Page
Tk_ImageChanged(3) Tk Library Procedures Tk_ImageChanged(3)__________________________________________________________________________________________________________________________________________________NAME
Tk_ImageChanged - notify widgets that image needs to be redrawn
SYNOPSIS
#include <tk.h>
Tk_ImageChanged(imageMaster, x, y, width, height, imageWidth, imageHeight)
ARGUMENTS
Tk_ImageMaster imageMaster (in) Token for image, which was passed to image's createProc when the image was created.
int x (in) X-coordinate of upper-left corner of region that needs redisplay (measured from upper-left corner
of image).
int y (in) Y-coordinate of upper-left corner of region that needs redisplay (measured from upper-left corner
of image).
int width (in) Width of region that needs to be redrawn, in pixels.
int height (in) Height of region that needs to be redrawn, in pixels.
int imageWidth (in) Current width of image, in pixels.
int imageHeight (in) Current height of image, in pixels.
_________________________________________________________________DESCRIPTION
An image manager calls Tk_ImageChanged for an image whenever anything happens that requires the image to be redrawn. As a result of call-
ing Tk_ImageChanged, any widgets using the image are notified so that they can redisplay themselves appropriately. The imageMaster argu-
ment identifies the image, and x, y, width, and height specify a rectangular region within the image that needs to be redrawn. imageWidth
and imageHeight specify the image's (new) size.
An image manager should call Tk_ImageChanged during its createProc to specify the image's initial size and to force redisplay if there are
existing instances for the image. If any of the pixel values in the image should change later on, Tk_ImageChanged should be called again
with x, y, width, and height values that cover all the pixels that changed. If the size of the image should change, then Tk_ImageChanged
must be called to indicate the new size, even if no pixels need to be redisplayed.
SEE ALSO
Tk_CreateImageType
KEYWORDS
images, redisplay, image size changes
Tk 4.0 Tk_ImageChanged(3)
Hi,
I have several folders full of image sequences from an animation.
The image frames are named Frame0001.png to Frame0900.png, somewhere along the way the images have been named in reverse order.
Is there a script that read the contents of a folder and renumber the files Frame0001.png -... (1 Reply)
I have images in PS that I want to convert to JPG (unfortunately, I need to use them in Powerpoint! :eek:). The problem is that the edges of the image get chopped off when I use:
convert filename.ps filename.jpg
So, for example, in my plots, the top and bottom labels for the x-axis are... (0 Replies)