[Brix]

I've just upgraded my project to newest Arc trunk (r866), it would seem that somebody has forgotten parts of some earlier patches, as trunk isn't compilable in its current state?

Anyway, here is the patches I currently use:
http://brix-verden.dk/d/arc/

They make trunk compilable, fixes the toRadians function (wrong name) in arc/sprite/sprite.d, and makes the Color struct usable with fonts.

- Brix

[ChristianK]

Thanks for those patches. I'm out for the day, but will look at them tomorrow. Indeed, I haven't checked consistency of the arc/sprite directory for all recent changes. I usually just compile some unittests and the asteroids example to see if things still work.

However, I'm glad to see you managed to get sprite to work again this easily.

[Brix]

I've just updated my patches against your texture updates (r867).
You forgot to change the normal image.draw function, so I've fixed this in my patches, and my project is now able to use 800x600 images perfectly.

- Brix

[clayasaurus]

If it is not fixed by then, I'll use these patches on the weekend.

If you have time, maybe you can create a Sprite unittest for us to use? I would but my time is limited, I might also try to make one this weekend though if its not done before then. A sprite unitttest would make sure we would make sure that the sprite class works with all the changes going on in the trunk.

Also...

Overall, I think I might want to go back to the old

func(r,g,b,a)

instead of

func(color)

because r, g, b, a values are just that much more versatile.

Thanks for using Arc! : )

[Brix]

[clayasaurus]

A sprite unittest is simply a main.d like file that tests all of the sprites functions possible and make the program crash if the unittest doesn't work right (best crash w/ err message )

I'll get it done this weekend I suppose.

When there are extensive changes made to the trunk, we like to test our code with the unittests because the unittests are designed to test each feature of one specific section of the library, if something goes wrong it is easy to tell or the unittest is designed to tell us what went wrong.

I guess we can use the color object for passing around, if you really find them that useful. Just sometimes seems like a hack to use

draw(Color(1,1,1,1))


and a lot of work to use
Color c = Color(255,0,0,255);

draw(c);

[ChristianK]

I've applied the patches.

I added the Color struct and switched (most of) the drawing functions to use them specifically to simplify declaring and passing them. The reasoning is really the same as with Point and Rect. It also has the advantage that we could add a set of standard colors to arc.draw.color.