From 0ceecc4fe80693169d343c6962c9f4247c1e61a3 Mon Sep 17 00:00:00 2001 From: Michael Miller Date: Sun, 17 Apr 2016 01:56:28 -0700 Subject: [PATCH] Updated Raster Image Support (markdown) --- Raster-Image-Support.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Raster-Image-Support.md b/Raster-Image-Support.md index e0e5b7b..ef293c1 100644 --- a/Raster-Image-Support.md +++ b/Raster-Image-Support.md @@ -2,10 +2,10 @@ Currently there are two primary objects exposed that help manage images. They each provide a solution to managing and rendering image data onto the strip. They both require a template 'Method' class that defines where and how the memory is managed. Their internal memory storage matches the pixel layout of the NeoPixelBus which provides a fast rendering. -## NeoBuffer object +## [NeoBuffer object](https://github.com/Makuna/NeoPixelBus/wiki/NeoBuffer-object) The NeoBuffer is basic image storage object. It can store the image data in RAM or reference image data stored in PROGMEM. It provides direct x,y access to set and get pixels along with a render method `Blt()` that will copy bits to the NeoPixelBus or other Raster objects. -## NeoVerticalSpriteSheet object +## [NeoVerticalSpriteSheet object](https://github.com/Makuna/NeoPixelBus/wiki/NeoVerticalSpriteSheet-object) The NeoVerticalSpriteSheet is used to abstract that the image actually contains a series of sprites of the same size. It can store the image data in RAM or reference image data stored in PROGMEM. It provides direct sprite,x,y access to set and get pixels along with a render method `Blt()` that will copy a sprite to the NeoPixelBus or other Raster objects.