Recent changes to max_current_image_order

WikiPage max_current_image_order modified by Björn Ståhl

Björn Ståhl — Sat, 16 Jun 2012 16:28:29 -0000

--- v2
+++ v3
@@ -12,6 +12,6 @@
 [order_image]
 
 **caveats:**
-There is a finite upper-lower limit to order (signed int, but caps at 0).
+There is a finite upper-lower limit to order (0 <= order < INTMAX_t).
 The reason for it being signed is that internally, 3D objects use an inverse negative order.

WikiPage max_current_image_order modified by Björn Ståhl

Björn Ståhl — Sat, 16 Jun 2012 16:27:37 -0000

--- v1
+++ v2
@@ -8,12 +8,10 @@
 
 The included support scripts use this function frequently.
 
-~~~~
-
 **related functions:**
 [order_image]
 
 **caveats:**
 There is a finite upper-lower limit to order (signed int, but caps at 0).
-The reason for it being signed is that internally, 3D objects use an inverse negative order (< 0).
+The reason for it being signed is that internally, 3D objects use an inverse negative order.

WikiPage max_current_image_order modified by Björn Ståhl

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

**declaration:** ~~~~ max_current_image_order() => orderv ~~~~ Sweeps through the current VID context, looking for the highest order value. This function is primarily used to push an object to the front in situations where you don't have predefined layers (e.g. background has order 0, sprites order 1, etc.) The included support scripts use this function frequently. ~~~~ **related functions:** [order_image] **caveats:** There is a finite upper-lower limit to order (signed int, but caps at 0). The reason for it being signed is that internally, 3D objects use an inverse negative order (< 0).