Recent changes to pop_video_context

WikiPage pop_video_context modified by Björn Ståhl

Björn Ståhl — Sat, 16 Jun 2012 10:58:57 -0000

--- v2
+++ v3
@@ -7,7 +7,7 @@
 Remove the current VID context from the stack, deallocated all associated resources. Returns the current active context number. This can be used for quick means of garbage collection / error recover.
 
 **related functions:**
-[push_video_context] [system_context_size]
+[push_video_context] [system_context_size] [current_context_usage]
 
 **changes / deprecations: **
 It is currently not possible to have any VIDs persist between context stacks, and this limits its use somewhat. Thus in future revisions, it may be possible for certain VIDs to be masked as persistant, preventing them from being deleted but also puts restrictions on being used in framesets/instancing etc.

WikiPage pop_video_context modified by Björn Ståhl

Björn Ståhl — Sat, 16 Jun 2012 10:57:13 -0000

--- v1
+++ v2
@@ -1,7 +1,7 @@
 **declaration:**
 
 ~~~~
- function pop_videocontext() => context index
+ function pop_video_context() => context index
 ~~~~
 
 Remove the current VID context from the stack, deallocated all associated resources. Returns the current active context number. This can be used for quick means of garbage collection / error recover.

WikiPage pop_video_context modified by Björn Ståhl

Björn Ståhl — Sat, 16 Jun 2012 10:55:48 -0000

**declaration:** ~~~~ function pop_videocontext() => context index ~~~~ Remove the current VID context from the stack, deallocated all associated resources. Returns the current active context number. This can be used for quick means of garbage collection / error recover. **related functions:** [push_video_context] [system_context_size] **changes / deprecations: ** It is currently not possible to have any VIDs persist between context stacks, and this limits its use somewhat. Thus in future revisions, it may be possible for certain VIDs to be masked as persistant, preventing them from being deleted but also puts restrictions on being used in framesets/instancing etc. **caveats:** The stack only applies for resources tied to VIDs, audio resources are tied to AIDs and thus managed in a separate namespace.