Revision history for KeyPgScreenunlock


Revision [21130]

Last edited on 2016-03-13 10:42:31 by fxm [Formatting]
Additions:





Revision [20512]

Edited on 2016-02-10 16:08:26 by DkLwikki [Update link format]
Additions:
[[KeyPgDeclare|declare]] [[KeyPgSub|sub]] **Screenunlock** ( [[KeyPgByval|byval]] //startline// [[KeyPgAs|as]] [[KeyPgLong|long]] = -1, [[KeyPgByval|byval]] //endline// [[KeyPgAs|as]] [[KeyPgLong|long]] = -1 )
##**Screenunlock**## unlocks the current work page assuming it was previously locked by calling ##[[KeyPgScreenlock|Screenlock]]## and lets the system restart updating the screen regularly. When called with ##start_line## and ##end_line## , only the screen area between those lines is assumed to have changed, and will be updated.
Calls to ##**Screenunlock**## must be paired with matching calls to ##**[[KeyPgScreenlock|Screenlock]]**##. Only the first call to ##**[[KeyPgScreenlock|Screenlock]]**## actually performs a locking operation. Subsequent calls to ##**Screenlock**## only increment the lock counter. Conversely, ##**Screenunlock**## only decrements the lock counter until it reaches zero at which time the actual unlock operation will be performed. Using ##[[KeyPgScreengraphics|Screen]]## or ##[[KeyPgScreenres|Screenres]]## will release all locks and set the lock counter back to zero before changing screen modes.
All graphic statements automatically lock the screen before the function call, and unlock the screen afterwards, so you do not need to do this explicitly using ##**[[KeyPgScreenlock|Screenlock]]**## and ##**Screenunlock**##. You only need to lock the screen when you wish to access the screen (framebuffer) directly using ##[[KeyPgScreenptr|Screenptr]]## or when you wish to group several graphic statements together so their effects appear simultaneously on screen, thus avoiding potential screen flicker during screen updates.
Warning (""Win32"", Linux) : The screen is locked by stopping the thread that processes also the OS' events. This means the screen should be locked only for the short time required to redraw it, and no user input will be received while the screen is locked. When the induced lock time becomes too long, use preferably the method of double buffering (with ##[[KeyPgScreencopy|Screencopy]]##).
See ##[[KeyPgScreenptr|Screenptr]]## example.
- Not available in the //[[CompilerOptlang|-lang qb]]// dialect unless referenced with the alias ##**""__Screenunlock""**##.
- ##[[KeyPgScreengraphics|Screen (Graphics)]]##
- ##[[KeyPgScreenlock|Screenlock]]##
- ##[[KeyPgScreenptr|Screenptr]]##
Deletions:
[[KeyPgDeclare declare]] [[KeyPgSub sub]] **Screenunlock** ( [[KeyPgByval byval]] //startline// [[KeyPgAs as]] [[KeyPgLong long]] = -1, [[KeyPgByval byval]] //endline// [[KeyPgAs as]] [[KeyPgLong long]] = -1 )
##**Screenunlock**## unlocks the current work page assuming it was previously locked by calling ##[[KeyPgScreenlock Screenlock]]## and lets the system restart updating the screen regularly. When called with ##start_line## and ##end_line## , only the screen area between those lines is assumed to have changed, and will be updated.
Calls to ##**Screenunlock**## must be paired with matching calls to ##**[[KeyPgScreenlock Screenlock]]**##. Only the first call to ##**[[KeyPgScreenlock Screenlock]]**## actually performs a locking operation. Subsequent calls to ##**Screenlock**## only increment the lock counter. Conversely, ##**Screenunlock**## only decrements the lock counter until it reaches zero at which time the actual unlock operation will be performed. Using ##[[KeyPgScreengraphics Screen]]## or ##[[KeyPgScreenres Screenres]]## will release all locks and set the lock counter back to zero before changing screen modes.
All graphic statements automatically lock the screen before the function call, and unlock the screen afterwards, so you do not need to do this explicitly using ##**[[KeyPgScreenlock Screenlock]]**## and ##**Screenunlock**##. You only need to lock the screen when you wish to access the screen (framebuffer) directly using ##[[KeyPgScreenptr Screenptr]]## or when you wish to group several graphic statements together so their effects appear simultaneously on screen, thus avoiding potential screen flicker during screen updates.
Warning (""Win32"", Linux) : The screen is locked by stopping the thread that processes also the OS' events. This means the screen should be locked only for the short time required to redraw it, and no user input will be received while the screen is locked. When the induced lock time becomes too long, use preferably the method of double buffering (with ##[[KeyPgScreencopy Screencopy]]##).
See ##[[KeyPgScreenptr Screenptr]]## example.
- Not available in the //[[CompilerOptlang -lang qb]]// dialect unless referenced with the alias ##**""__Screenunlock""**##.
- ##[[KeyPgScreengraphics Screen (Graphics)]]##
- ##[[KeyPgScreenlock Screenlock]]##
- ##[[KeyPgScreenptr Screenptr]]##


Revision [17548]

Edited on 2015-04-01 13:03:56 by DkLwikki [integer => long]
Additions:
[[KeyPgDeclare declare]] [[KeyPgSub sub]] **Screenunlock** ( [[KeyPgByval byval]] //startline// [[KeyPgAs as]] [[KeyPgLong long]] = -1, [[KeyPgByval byval]] //endline// [[KeyPgAs as]] [[KeyPgLong long]] = -1 )
Deletions:
[[KeyPgDeclare declare]] [[KeyPgSub sub]] **Screenunlock** ( [[KeyPgByval byval]] //startline// [[KeyPgAs as]] [[KeyPgInteger integer]] = -1, [[KeyPgByval byval]] //endline// [[KeyPgAs as]] [[KeyPgInteger integer]] = -1 )


Revision [15953]

Edited on 2012-02-02 11:51:49 by CountingPine [Remove implicit CamelCase link]
Additions:
Warning (""Win32"", Linux) : The screen is locked by stopping the thread that processes also the OS' events. This means the screen should be locked only for the short time required to redraw it, and no user input will be received while the screen is locked. When the induced lock time becomes too long, use preferably the method of double buffering (with ##[[KeyPgScreencopy Screencopy]]##).
Deletions:
Warning (Win32, Linux) : The screen is locked by stopping the thread that processes also the OS' events. This means the screen should be locked only for the short time required to redraw it, and no user input will be received while the screen is locked. When the induced lock time becomes too long, use preferably the method of double buffering (with ##[[KeyPgScreencopy Screencopy]]##).


Revision [15339]

Edited on 2011-10-03 06:18:21 by FxMwikki [Comment about an alternative method (double buffering) when the screen lock time is too long]
Additions:
Warning (Win32, Linux) : The screen is locked by stopping the thread that processes also the OS' events. This means the screen should be locked only for the short time required to redraw it, and no user input will be received while the screen is locked. When the induced lock time becomes too long, use preferably the method of double buffering (with ##[[KeyPgScreencopy Screencopy]]##).
Deletions:
Warning (Win32, Linux) : The screen is locked by stopping the thread that processes also the OS' events. This means the screen should be locked only for the short time required to redraw it, and no user input will be received while the screen is locked.


Revision [14835]

Edited on 2010-09-24 22:40:04 by Sisophon2001 [Rewrote one paragraph and removed abbreviation]
Additions:
Calls to ##**Screenunlock**## must be paired with matching calls to ##**[[KeyPgScreenlock Screenlock]]**##. Only the first call to ##**[[KeyPgScreenlock Screenlock]]**## actually performs a locking operation. Subsequent calls to ##**Screenlock**## only increment the lock counter. Conversely, ##**Screenunlock**## only decrements the lock counter until it reaches zero at which time the actual unlock operation will be performed. Using ##[[KeyPgScreengraphics Screen]]## or ##[[KeyPgScreenres Screenres]]## will release all locks and set the lock counter back to zero before changing screen modes.
All graphic statements automatically lock the screen before the function call, and unlock the screen afterwards, so you do not need to do this explicitly using ##**[[KeyPgScreenlock Screenlock]]**## and ##**Screenunlock**##. You only need to lock the screen when you wish to access the screen (framebuffer) directly using ##[[KeyPgScreenptr Screenptr]]## or when you wish to group several graphic statements together so their effects appear simultaneously on screen, thus avoiding potential screen flicker during screen updates.
Deletions:
Calls to ##**Screenunlock**## must be paired with a matching call to ##**[[KeyPgScreenlock Screenlock]]**##. Only the first call to ##**[[KeyPgScreenlock Screenlock]]**## actually performs a locking operation. Subsequent calls to ##**Screenlock**## only increment the counter. Conversely, ##**Screenunlock**## only decrements the lock counter until it reaches zero at which time the actual unlock operation will be performed. Using ##[[KeyPgScreengraphics Screen]]## or ##[[KeyPgScreenres Screenres]]## will release all locks and set the lock counter back to zero before changing screen modes.
After ##**Screenunlock**## is called, all graphics statements still may be safely used, OTOH accessing the work page framebuffer directly via ##[[KeyPgScreenptr Screenptr]]## may only be used after locking the screen again with ##[[KeyPgScreenlock Screenlock]]##.


Revision [14445]

Edited on 2009-08-29 21:57:05 by CountingPine [Remove CamelCase links in "New to FreeBASIC"]
Additions:
- New to ""FreeBASIC""
Deletions:
- New to FreeBASIC


Revision [13704]

Edited on 2008-09-07 12:29:59 by JeffMarshall [updated information on nested screenlocks]
Additions:
An internal counter exists that remembers the screen lock state, thus ##**Screenunlock**## has an effect only on a screen that is locked. A screen that has not been locked with ##**Screenlock**## cannot get unlocked, however ##**Screenunlock**## still will force an update of given area or full screen.
Calls to ##**Screenunlock**## must be paired with a matching call to ##**[[KeyPgScreenlock Screenlock]]**##. Only the first call to ##**[[KeyPgScreenlock Screenlock]]**## actually performs a locking operation. Subsequent calls to ##**Screenlock**## only increment the counter. Conversely, ##**Screenunlock**## only decrements the lock counter until it reaches zero at which time the actual unlock operation will be performed. Using ##[[KeyPgScreengraphics Screen]]## or ##[[KeyPgScreenres Screenres]]## will release all locks and set the lock counter back to zero before changing screen modes.
Deletions:
An internal flag exists remembering the screen lock state, thus ##**Screenunlock**## has an effect only on a screen that is locked - or in other words, a screen that is not locked with ##**Screenlock**## cannot get unlocked, however ##**Screenunlock**## still will force an update of given area or full screen.


Revision [13357]

The oldest known version of this page was created on 2008-05-11 09:06:26 by DoS386 [updated information on nested screenlocks]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki



sf.net phatcode