Quote:
Originally Posted by Stefan
You shouldn't use pics1.png though, Graal only reads its pixels into a buffer but doesn't use the alpha or transparency values, it's not creating a texture for it either. So it would be better to use several separated tiles images may be, although for v3.1 I also plan to add a command for drawing tiles (including the addtiledef things) into a drawing panel.
|
You're probably right about pics1.png. It would probably do to make a brand new window script that shows images that contains an array in it's initialization that define x and y values (arrived at from scrolling) of any image and the specific image. Also, maybe inner width and height. Scroll rounding wouldn't be something I would put into a typical window script, but it works for a tile editor script.
Let me tell you that it's quite a bit easier to use one image, but just not as dynamic.
Now that I think about it, you could probably use the tile selector concepts from me in the default editor. Graal's tile selector can be at zero width or height or both. I wanted to evade that, so I just made it so that there's always at least one square selected, which would be the square first clicked on. I had to change the initial mousex,mousey saved values to do that though which scared me a little bit, but worked. In any other situation I'd probably make new values.