Images

Images are represented by the Image class. In Cascades, you have two types of images: images that are assets (packaged with an application) and external images (generated by the app, or coming from other sources). The behavior of these two types and the process for creating them differs.

Typically, you should use image assets for any images that are used to build your UI (for example, backgrounds, icons, borders, and so on). When you load an image from an asset, it's almost instantly available.

If you don't use assets for building your UI, the images are loaded asynchronously. In some cases, the images might be displayed a short time after the rest of your UI.

Images in memory

In Cascades, images that are loaded into memory are stored in a texture cache. If your application ever reaches a low-memory state, the application might remove images from the cache that aren't currently visible on the screen. The size and position of these images are maintained in the scene graph to minimize the impact on an application's layout. When those screens become visible again, the application might use an animation effect to display the images that had been removed.