Version 0.3.2
LÖVE Documentation
OverviewLicenseCreditsInstallingGetting started
Devices
love.graphicslove.audiolove.keyboardlove.mouselove.filesystemlove.timerlove.system
Types
AnimationColorFontFileImageMusicParticleSystemSound
Callbacks
loadupdatedrawmousepressedmousereleasedkeypressedkeyreleased
Miscellaneous
ConstantsConfig filesKeyboard shortcuts
Function
love.graphics.setMode( width, height, fullscreen, vsync, fsaa )
Do not change the display mode unless you know that that mode is supported. Use checkMode() to check whether a mode is supported or not.

Also note that calling this function will cause the entire display context to reload. This means that all Images, Fonts and other graphical objects will have to be reloaded. It is therefore advisable to call this function when as few objects as possible has been loaded.

FSAA stands for Full Scene Anti-Aliasing, and it is recommended to set this number to 0 (the default), unless you need anti-aliasing of the edges on primitves and images. Most machines who support this feature support 1, 2 and 4 FSAA buffers. The more buffers, the better the anti-aliasing and the slower the performance. Assuming you're not using filled primites, you do not really need FSAA as long as you pad the sprites with some empty space; in this case FSAA will have no effect on the visuals at all, it will only hinder performance.
Usage
love.graphics.setMode( width, height, fullscreen, vsync, fsaa )
Arguments
widthDisplay width.
heightDisplay height.
fullscreenFullscreen (true), or windowed (false).
vsyncTrue if LOVE should wait for vsync, false otherwise (normally true).
fsaaThe number of FSAA-buffers (normally 0).
Returns
booleanTrue if successful, false otherwise
Examples
Example 1: Changing the display mode. function keypressed(k)
if k == love.key_up then
   -- Set a display mode with 1024x768 resolution,
   -- no fullscreen, vertical sync on if possible,
   -- and no FSAA (anti-aliasing) disabled. Unless you need
   love.graphics.setMode(1024, 768, false, true, 0)
end