This topic contains 17 replies, has 12 voices, and was last updated by 
Danilo
2 years, 8 months ago.
-
Posts
-
Regarding image assets. Is not the de facto standard to use sprite sheets these days, anyone not using that and calling a direct LoadImage? I see it simplifies the dev flow a lot, but also near needed for performance & memory for flash/ecmacript/ios/android? Then image loading can use the spritesheet “local” scope instead of a path.
So instead of a long list of Open/Load
local sprites:= Assets.LoadSpritesheet(“MySpriteSheet”)
sprites.Render(“Starship1”, x , y, direction)
Flash is dead
a sprite sheet is really just an image with some form of subimage reference system
Spritesheets are probably more used in games,
and MX2 is (and should be) not limited to games only.In Windows you would call it ImageList for using
with Toolbars, etc.IncBin that creates an C++ array or memory-pointer would be nice,
for loading assets/data (images/sounds/music/sprites/txt/ico/cur/…) directly
from memory, using a memory address (void ptr).
Especially to create stand-alone executables on the desktop-targets.
You must be logged in to reply to this topic.