Recent changes to load_image_asynch

WikiPage load_image_asynch modified by Björn Ståhl

Björn Ståhl — Thu, 21 Jun 2012 20:23:56 -0000

--- v2
+++ v3
@@ -25,7 +25,7 @@
 ~~~~
 
 **related functions:**
-[load_image_async]
+[load_image_asynch]
 
 **caveats:**
 Same as [load_image], but also that there's no argument for specifying order, [order_image] have to be called explicitly. Before the callback has been called the first time, surface storage properties are undefined.

WikiPage load_image_asynch modified by Björn Ståhl

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

--- v1
+++ v2
@@ -1,4 +1,4 @@
-**definition:**
+**declaration:**
 
 ~~~~
 load_image_asynch(resource, [callback] ) => VID

WikiPage load_image_asynch modified by Björn Ståhl

Björn Ståhl — Sat, 16 Jun 2012 09:14:03 -0000

**definition:** ~~~~ load_image_asynch(resource, [callback] ) => VID ~~~~ Loads a resource as an image asynchronously. If a [callback] function is specified, otherwise a video_event will be emitted, it will be invocated when the image status is changed -- either loaded or failed. The callback function is expected to look like: ~~~~ function imageload_cb(sourcevid, statustbl) statustbl.kind == "load_failed" or "loaded" statustbl.width == image actual width statustbl.height == image actual height end **example use:** ~~~~ vid = load_image_asynch(resource, function(source, statuslbl) if ); show_image(vid); ~~~~ **related functions:** [load_image_async] **caveats:** Same as [load_image], but also that there's no argument for specifying order, [order_image] have to be called explicitly. Before the callback has been called the first time, surface storage properties are undefined. Some functions, like an external launch, may force an asynchronous push, forcing the image to load fully before proceeding. Any error that would have forced [load_image] to return BADID, will result in a blank (32x32) texture.