GfxLib - FreeBASIC graphics library overview
GfxLib is the built-in graphics library included in FreeBASIC. As well as re-creating every QuickBASIC graphics command, GfxLib has built-in commands to handle input from the keyboard and mouse. Major contributors of the library are Lillo, CoderJeff and DrV.
The library supports various drivers depending on the platform:

- All:
  - `Null` Does nothing, allows to use graphics functions on in-memory buffers and such, without anything being displayed in a graphics window. (gfxlib2/driver_null.c)
- Win32:
  - `DirectX` The default selection of FB GfxLib. May not be available on old Windows installations. (gfxlib2/driver_ddraw_win32.c)
  - `GDI` The "safest" one, available in all Win32 versions. Bug note: broken in FB versions 0.20 and (some ?) 0.18.x ("banding effects"), not fixed in 0.21 SVN (needs retest with 0.23). (forum discussion: p=106600) (gfxlib2/driver_gdi_win32.c)
  - `OpenGL` (gfxlib2/driver_opengl_win32.c)
- Linux & others:
  - `X11` The default on Unix systems (gfxlib2/driver_x11.c)
  - `OpenGL` (on top of X11) (gfxlib2/driver_opengl_x11.c)
  - `FBDev` Linux framebuffer device -- fallback in case X11 is disabled (gfxlib2/driver_fbdev_linux.c)
- DOS:
  - `BIOS` (gfxlib2/driver_bios_dos.c)
  - `ModeX` "tuned" 320x240x8bpp VGA mode (gfxlib2/driver_modex_dos.c)
  - `VESA banked` compatible with very old VESA 1.x implementations (gfxlib2/driver_vesa_bnk_dos.c)
  - `VESA linear` needs VESA version at least 2.0, usually faster than banked VESA (gfxlib2/driver_vesa_lin_dos.c)
  - `VGA` (gfxlib2/driver_vga_dos.c)
  - Bug note: Palette doesn't work well (forum discussion: t=12691 2008) (forum discussion: t=19980 2012)

`ScreenControl` can be used (SET_DRIVER_NAME 103) to override the default driver preferences.
Platform Differences

- In DOS, GfxLib will create and "manage" a mouse arrow if a mouse driver is detected. There is no "official" way to disable this. Also the arrow doesn't react to mouse movements while the screen is locked.
- In DOS, Windowing and OpenGL related commands and switches are not available (they exist but do nothing, or return some values with no meaning)
- In DOS, the resolution must match one supported by the graphics card. GfxLib will try to find an appropriate mode from VGA modes, ModeX or VESA, preferring VESA LFB interface if available, or banked VESA otherwise. Unsupported resolutions may currently crash the program, though in future GfxLib may try to find a close match instead. For optimal compatibility, you should support "safe" resolutions like 640x480 and 800x600, and maybe 1024x768. There are various additional modes like 768x576 around, but they are vendor specific and lacking on many other cards. Also modes 1024x768 and above are not available on older cards and laptops.

Differences from QB

- Graphics support was internally redesigned. QB used VGA graphics modes, and wrote directly into the VGA RAM. Multiple pages were available as long as the card supported them. FB uses backbuffers, one per defined page, and copies them to the video RAM (VGA (DOS), VESA (DOS), DirectX (Win32), ...) in the background. Graphics commands do work as they used to in QB, but a few notable differences are present:
  - The background screen updating eats a considerable amount of CPU performance.
  - There is a thread (Win32 and Linux) or ISR (DOS, uses the PIT) active for this.
  - Mixing FB's graphics support with low-level screen accesses (VGA) is not supported, even in DOS. However direct screen memory access is possible using Screenptr and Screenlock and is fully portable. In DOS VGA and VESA are still available, but can't be mixed with FB's graphics support.

See also

- GFX Functions Index
- `Screen` The QB-like way to set graphics mode
- `ScreenRes` More flexible alternative to `Screen`
- `ScreenList` Check display modes available for FB GfxLib to use
- `ScreenControl` Select driver and more
- `ScreenLock`
- `ScreenUnlock`
- `ScreenPtr` Semi-low level access
- `ScreenSet`
- `ScreenCopy`
- `ScreenInfo`
- `ScreenGLProc`
- `Internal pixel formats`