id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
445	psImageCut's new prototype and use of psPixels	robert.desonia@…	Paul Price	"the prototype for psImageCut has changed in two ways:

1.  two psVectors, cutCols and cutRows, was replaced by a single psVector*
coords.  This however is a problem, a single psVector can't possibly hold both x
and y coordinates sans some odd encoding.  I'd use psPixels, but that is defined
with only integer coordinate values.  What do you want to do here?

2. four parameters giving the start and end coordinates of the cut were replaced
by a single psRegion.  Though this is feasible, this is not the typical
definition of psRegion, i.e., an image region.  Should there be a struct that
just represents a point (x,y)?  psPixelCoord is very close to what we really
need, though again, it is limited by the x & y being integer.  

Is there a grand reason why psPixels/psPixelCoord couldn't store x & y in
floating-point so it could be used more widely, e.g., here?

-rdd"	defect	closed	high		PSLib SDRS	unspecified	normal	fixed