Chapter 6. Known Problems
Prev |  | Next

## Chapter 6. Known Problems

First, a few general comments:

- It goes without saying that any bugs in the FOX library will be exposed in FXPy as well.

- FXPy is pretty highly coupled with FOX, and so you need to be careful about which versions of FXPy and FOX you're using together. Any of the FXPy-1.0.x releases should work with any of the fox-1.0.x releases, since the FOX 1.0 API is stable. However, if you need to use FXPy with a development version of FOX, be sure that the version numbers for both are compatible.

- All of the test programs run, but some of them don't quite work properly. For example, the `image.py` test shows the wrong images. So sue me, I'm working on it :)

The following FOX features (including some class member functions) are currently not supported by FXPy. They will probably be supported in a future release of FXPy unless there is some overwhelming technical reason not to do so.

- `FXVec`, `FXDVec`, `FXRange`, `FXHMat`, `FXDHMat`, `FXHVec`, `FXDHVec`, `FXQuat` and `FXDQuat` are not implemented.

- Although the `FXStream` and `FXFileStream` classes are exposed to Python to a limited degree, you can't really mix and match Python serialization with FOX's serialization. For an example of how you can use FOX stream objects from Python, see the `imageviewer.py` test program, where we use an `FXFileStream` object to load and save the image data.

- For `FXGLViewer`, the `getZSortFunc()`, and `setZSortFunc()` functions are not yet implemented.

- For `FXGLTriangleMesh`, the `setVertexBuffer()`, `setColorBuffer()`, `setNormalBuffer()`, `setTextureCoordBuffer()`, `getVertexBuffer()`, `getColorBuffer()`, `getNormalBuffer()` and `getTextureCoordBuffer()` functions need to be fixed.

- The static member function `FXFont.listFonts()` is missing.

Prev | Up | Next
Chapter 5. How is FXPy Different From FOX? | Home | Chapter 7. To-do List