#3 Incorrect behavior with multiple-displays on Mac OS X

[Sean Morrison]

Running the example/demo applications, a handful of
problems were observed when running on a dual-display
system running Mac OS X 10.3.

Several of the examples (about half) flat-out segfaulted
(sorry, no stack traces), though it's not certain that they
crashed because of the dual displays. There were, however,
clearly unexpected and incorrect behaviors in the ones that
did run.

First, for the demos that entered full-screen mode, they
choose to use the second display instead of the primary
(primary is defined by the system, and is the one that
provides the menubar). While this is not necessarily
"wrong", it was unexpected.

Next, it appears that the dual display settings mess up the
tracking and assumed screen dimensions. Certain examples
such as the input tracker that has a water fountain, tracked
into the wrong location (i.e. not in the boxes but, rather, to
the right somewhat). For all of the apps, the horizontal
trackball movement also behaved as if the width of the
window was the combination of the two windows width,
whereas the vertical motion was fine (the monitors are
aligned horizontally with similar vertical resolutions).

If I disconnect the secondary monitor and rerun the
examples, things are better, but there are still issues.
Depending on the location of the Dock, the "fullscreen"
windows do not completely overlay/cover the entire display
area (the dock is still displayed, as is the menu). This again
causes the tracking and positioning to be offset incorrectly.

Cheers!