Re: FXPoint

A comment was received:

  FXPoint's values should be upgraded to 32-bit (FXuint)

  In most graphics APIs (like OpenGL), polygons' X/Y
  coordinates can be stored in integers.

  But in FOX, polygon X/Y coords are only short, which means they are 
more
  limited, Or if you're trying to adapt an existing API around FOX, this
  may also require downcasting

The chosed coordinate representation was not *my* choice; rather, it was 
dictated
by the underlying drawing platforms [X11, or GDI].

In addition, whereever possible, the structure layout of FXPoint, 
FXSize, as well as FXRectangle is such that they can be mapped to 
similarly declared data structures
in the drawing API; this obviates the need to allocate temporary 
structures or arrays
of structures, copying the data, and then deleting them again.

In terms of coordinate range, for now, short is big enough.

OpenGL can handle coordinates in GLdouble, GLfloat, GLint, and GLshort. 
(e.g.
glRasterPos2sv(), or glVertex2s(), etc.).

So the problem may not be as big as you think...


Cheers,

     -- JVZ