Step 1) Bounding Box Collision - It's Faster. Find whether or not the two sprites' bounding boxes overlap and return two collision regions if they do. Step 2) Search within the collision region pixel by pixel and see if sprite1.pixelColor != 0 and sprite2.pixelColor != 0. If so, then there is colli...

How do i do it? I don't want the player to go like 'argh! i wanted to select that enemy but clicked on the next turn button!' just because the button click field is a square while the actual visual button is a circle. that's just an example. there's a lot of these problems in my code since i simply ...

i don't know if this should go into the beginners section or the lib, but i'll post it here. I did just download allegro, gonna try it out after the weekend. While the documentation surely will be of much help, anyone who has the time are welcome to post ideas of in which corner of this lib i should...

This is wonderful. I could even build a simple s+s synthesizer with this, technically, if i knew more about implementing MIDI in fb. :D
Thank you very much!

In my case, i could leave that as an option for the player to decide. It depends on what time penalties this would cause but in the end i don't want to cut off any improvement for those who have the possibility to view more smooth graphics without having the game running slower.

this is something i want to go further into aswell:

is the built-in lib fast enough for scaling, rotating, scrolling, and a couple of layers all at once in higher resolution?

is there a good method varying the pitch of a looping wav sample? I'm getting three steps ahead of myself now, but this would be pretty useful in a context where a, in my example, a tank which will race over a hill at a constant speed, does it so fast that it leaves ground for a while when going dow...

Is there a good, efficient way to smooth the pixels, and reduce that sawtooth effect, when resizing the object?

Isn't of much help for me right now though (there's one more except me in my country on that map now); this forum's list is a lot better. But thanks a lot for posting the link anyway!

I like the idea... if more people just would register their names and location there then that would be great.

Searching for the keywords in the line of erroneous code is too much of a strain for you? Not really, but it is not much of a strain to expand the manual a bit either. A little won't do any damage, right? How is the compiler supposed to know if the error is actually what the error is? Now that part...

Now this would take a lot of time to write, but would certainly at the same time make people waste a lot less time on the path of trial and error. now there's 224 errors and 26 compiler warnings. A lot of it is pretty self explanatory, but i think it would be a great idea if each error code would li...

I may be old and grumpy, but why not make a shout-out? I bet 75% of the members on this forum aren't active anyway. Just posting "who here is from madeupistan?" would catch the eye of anyone who is interested. That would certainly work... for me that is. But the problem remains unsolved, ...

Well, i don't have a ton of switches i want to be booleans, so wasting memory isn't really a problem, but it would certainly make the code more easy to read using them.

---

Thanks everybody. And keep on posting if anything else in this subject comes to your mind.

people doesn't seem to afford it whatsoever. there's daily reports of people dying en masse of simple and 'harmless' deceases which can easily be cured with stuff that's concidered to be cheap. :/

jofers wrote: However, having a strongly enforced BOOL type has its benefits though, and something like C++-style enumerations would be a nice feature that could implement that.

You lost me at c++-style enumerations, i don't know a bit about that language.

So there's no way to access those unused bytes, then?