id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
371	psPixels	robert.desonia@…	Paul Price	"Possible enhancement:

Currently, psPixels is defined merely as two psVectors, one for x, and one as y
coordinates.

To efficiently qsort the pixels (as required for psPixelsConcatenate), I found
it advantageous to transfer the data into an array of x,y pair structs, i.e.,

typedef struct {
    psS32 x;
    psS32 y;
} pixelCoord;
...
pixelCoord coordinates[length];
...

This prompts the question, would it not be better if psPixels had the same
structure?  I.e., 

typedef struct {
    int n;
    int nalloc;
    psPixelCoord* data;
} psPixels;

This would eliminate many things that I otherwise have to deal with, including
size mismatches and multiple type-support of the psVectors in the old
definition,  It would also allow a qsort in-place, eliminating the need for a
shadow buffer for concatenation, etc.

Another option is to modify psVector (or psArray) to have support for x,y pairs
by adding the pixelCoords struct in the data union, and use that instead of
psPixels.

-rdd"	enhancement	closed	high		PSLib SDRS	unspecified	minor	fixed