diff options
author | Colin Okay <colin@cicadas.surf> | 2022-07-16 09:21:34 -0500 |
---|---|---|
committer | Colin Okay <colin@cicadas.surf> | 2022-07-16 09:21:34 -0500 |
commit | 91a7fd9f7bb347d2c4d9652e443a3d485ccf4da3 (patch) | |
tree | 7583cd4c9c9047dfb9313e77326760e56d39306f | |
parent | b20698fa4cc47bc092b54a338aa37f8771ddf091 (diff) |
[doc] updated the readme
-rw-r--r-- | README.org | 3 |
1 files changed, 1 insertions, 2 deletions
@@ -140,13 +140,13 @@ More specifically, you can use the following accessor functions on them: There are a few convenience functions also defined that use the above functions under-the-hood. I'm not including them here because the API is still stabilizing. - The affine units are things like: + ~bitmap~: display an image that has been loaded from a file asset (currently only png is supported) + ~text~: display text + ~frameset~: display an animated sequence of images + ~sprite~: display a "bundle" of framesets ++ ~canvas~: display a region of mutable pixels *** Events & Event Handling @@ -258,7 +258,6 @@ Likewise you can drop an event handler If ~handler-or-event-type~ is an event handler instance, it is removed if present. If ~handler-or-event-type~ is symbol whose ~symbol-name~ is the name of an event (e.g. ~:mousedown~ or ~'perframe~), then all handlers of that type are removed from the unit. - *** The Asset Protocol Assets are resources loaded from disk. The application's ~asset-classifiers~ list associates file extensions (like "ttf", and "png") with classes (like ~font~ and ~png~) that load and prepare assets for use in an application. |