DISPLAY-X(7ggi)

NAME
display-x, display-xlib - Displays in an X window

SYNOPSIS

display-x : [ [ -inroot ] [ -inwin=winid ] [ -noinput ] [ -nocursor ] [ -physz==sizex,sizeydpi ] ] [ display ]

display-xlib : [ [ -inroot ] [ -inwin=winid ] [ -noinput ] [ -nocursor ] [ -physz==sizex,sizeydpi ] ] [ display ]

DESCRIPTION

display-x opens an X window and emulates a linear framebuffer which is blitted to the X server with the XPutImage function. In asynchronous mode this is done when ggiFlush is called, and in synchronous mode it is done periodically in the background (with the framerate specified by GGI_MANSYNC_FPS. The MITSHM extension is used when available for maximum speed.

display-xlib opens an window and uses Xlib primitives to do drawing. It is faster than display-x when using drawing primitives on on accelerated X server, but blitting is slower when running local to the X server.

In both targets, Ctrl+Alt+m toggles mouse grabbing. It will try to emulate a "relative" mouse device, i.e. one that can be moved arbitrarily far in any direction without ever leaving the window. This is useful for game controls, where loosing focus is generally undesireable. Note that grabbing must be turned off in order to leave the window.

OPTIONS

display
    The X display to connect to, otherwise defaults to the display specified in DISPLAY

-inroot
    Run in root window

-inwin=winid
    Run in already-existing window with id winid

-noinput
    X events sent to the window are not captured and merged with any other LibGII input sources. This allows one to take input from raw devices without receiving duplicate events should X also be configured to use the device.

-nocursor
    Normal behavior of display-x and display-xlib is to create a small dot mouse cursor pixmap which is visible when the mouse is positioned over the window containing the visual. This goes away when using mouse grabbing as described above, but otherwise can get in the way of mouse cursors implemented by the application. With this option, the X mouse cursor will be invisible when it is over the visual.

-physz==sizex,sizeydpi
    This option will override the physical screen size reported by the X server, which affects applications which wish to remain resolution independent. sizex,sizey are the x,y size of the entire screen (not just the X window containing the visual) in millimeters, unless the optional dpi string is affixed, in which case, they represent resolution in dots-per-inch. Yes, there are two equals signs there, for reasons of compatibility with other targets.

FEATURES

  FOR DISPLAY-X
DirectBuffer always available. Unaccelerated Multiple frames Panning

  FOR DISPLAY-XLIB
DirectBuffer never available. Accelerated if the hosting X server is.