here is the extension:
(props to @MKleinSB for the oled extension)
(i changed it a little, adding diffrent dimensions of images, and making the draw function have a black background instead of a transparent one)
ill explain the blocks later.
(its very confusing to understand on your own, so i suggest that you should not use it until i explain how it works)
Why does it need to be a different thing for OLED?
wdym?
The micro:bit doesn’t have a graphical screen, but a grid of LEDs, and you can’t really show a tile map on it so those blocks aren’t added. But you can add a screen onto the micro:bit, and I think the extensions allows you to make tile maps for the applied screen. Not sure why it’s specifically for OLEDs though.
i’m gonna explain the blocks.
sets the tile images.
these (of course) adds and removes tiles.
sets the layout of the tilemap, the tiles are represented by ascii characters. (for example, the first tile is " " (space) and the second is “!” and the third is “*” and so on.)
(an example of a layout:
*
!!!!!!!!!!!
!!!
!!!!!!!!!!!!!!!!
)
gets the image for the tile.
(and also, the tile sizes should be 8x8)
gets ascii character from x and y.
draws the tilemap on the buffer.
these two are not related to tilemaps. the long one gets two areas and detects if they’re colliding to each other or not. and the short one gets a normal x and y position (which becomes an 8x8 area), and gets a tilemap position, and checks if they collide or not.
these set and change the camera position
this replace the tile (as the an ascii character) at the position.
and this, is the same as “get_tilemap”. (idk why i didnt delete this block.)
and thats all!
Can you post an example?
Thanks for your Work!
Michael
fun fact: i was gonna go for a week or two. and i am actually gonna go for a week or two (by “go”, i mean not be online)
uuuuummm… does it work for the micro car oled screen. becouse it not working for me