Hey all,

I can't get gem to create a fullscreen window on the second display on OSX. The fullscreen method seems to change nothing visually, but the gemwin "print" method does print out "fullscreen = 1".

I'm using gem CVS from about a week ago, with Jamie's new additions that give the "gemwin" a title-bar.

I am not using pd++ since It kept crashing on my machine when I tried to use flags.

Can anyone shed any light?

Oh and the "offset message" does not seem to work correctly. If I open a window on the second screen with the offset 1280+0 I get a window that is about 20 pixels from the top of the screen. (perhaps the y offset's origin is the bottom of the menu-bar not the top of the screen?) In order to get the gemwin title bar near the top of the screen I need to use a negative y offset (-25 or so). Another interesting thing is that when I do this apears a space at the bottom of the gemwin! Ok I did a little more investigation:

Creating a 500x500 window with offset +0+0 we get:

a Gemwin that is acually 500x450 pixels (not including the titlebar)

It also happens that the distance between the top of the imagearea in the gemwin (just below titlebar) is exactly 50 pixels from the very top of the screen.

Also I looked a little deeper and I think I know whats happening with the pix_snap2tex curruption. The distance the snaped texture is offset is about 50 pixels over Y. So what pix_snap is doing is grabbing 500x500 pixels, but only 500x450 of this is actually a gl context, so we get garbage in the area above the context (the 50 pixels of titlebar and apple menubar.)

I can make an image to illustrate this in case anyone is confused. I think solving the gemwin dimention problem will solve the pix_snap2tex problem.

Please take a look! Thanks

Ben