2.4.7.3 Final Notes
This section lists future plans as well as problems or potential problems with
the BeOS port of Crystal Space.
-
Now that the engine supports window resizing, the BeOS 2D drivers should
also support this feature. Also enable the "zoom" button on the window.
-
Pause when not the foreground application. Make sure that screen redraws
correctly even when paused.
-
Add full-screen support for software mode. Be careful about the resolution,
since Crystal Space can use any arbitrary window dimension.
-
The various 2D graphics drivers (software, OpenGL) should all be
derived from a common class rather than being nearly identical copies of one
another.
-
Technically, the software 2D drivers should be employing
double-buffering since a window-exposed event in the sub-thread which is
running the `BApplication' will draw using the `BBitmap' even though
the main thread, in which Crystal Space is running, may be in the process of
updating the bitmap. This thread-unsafe behavior could lead to visual
anomalies.
-
Not all key combinations generate
KeyDown()
and KeyUp()
events,
yet Crystal Space applications may want to intercept them. For instance,
MazeD expects to responds to the keystrokes CTRL-1,
CTRL-2, etc., yet these key combinations are not seen by the
system driver since KeyUp()
and KeyDown()
are never called in
the canvas view subclasses To fix this, it should be possible to intercept
such keystrokes in MessageReceived()
within each `BView' subclass
in the 2D driver and respond directly to the `B_UNMAPPED_KEY_DOWN' and
`B_UNMAPPED_KEY_UP' messages.
-
Consider using `DirectWindow' rather than `DirectBitmap', where
supported, since `DirectWindow' puts much less load on the CPU.
Auto-detect if `DirectWindow' is available and use it if so. Note,
though, that David Huen says this might not be worthwhile on account of the
fact that the software renderer reads from the frame buffer, and this can be a
slow operation on some hardware.
-
It is possible to depress the window's close button while Crystal Space is
still initializing, however the close button is ignored until the Crystal
Space event loop is activated--at which time Crystal Space processes the
window-close event. It might be worthwhile to offer the user the option to
forcibly kill the application in this case, but at the very least the user
must be warned that doing so might corrupt data on disk (for instance, if
the engine is updating a ZIP file on a VFS volume.
-
Ked Shayer (c.shayer2@ukonline.co.uk) suggests using NASM for
the assembler code.
This document was generated
using texi2html