Oooops... I thought it was already removed (I remember reading about the *intention*...)

Anyway, I still think LÖVE should be a "safe" application. I still open .love files without thinking twice, at least for now...

I thought rotating around a non-centre point was done using image:setCenter() and then rotating.

Or is the question "why do we have to call setCenter() on the image (stateful) and we don't have a function for that (stateless)"?

Thank you very much! It solved the problem immediately...

Now I'm happy again

Thanks for that... much easier than my original conversion.

I've been using Lua for some time now (a few years) but have never explored the math library - initially I was using an integer-only version that was running on an embedded system, so the math library was simply not available.

I was responding more to cag, really. There's a problem here: on the one hand a file browser doesn't sounds like a feature consistent with the rest of the API. On the other hand, allowing developers to write such a feature means that there's some way to load/save files (even if has to be enabled in ...

I quite like the simplicity of clicking on a .love attachment and running it without wondering which files are going to be overwritten this time (or read and sent over the net using LuaSocket...) Of course, we have many programs that write to files and we don't expect them to ask "are you sure?...

Thanks for the suggestion. Unfortunately it doesn't help - the cursor is still outside the rectangle most of the time.

I guess for now I'll have to draw the cursor myself - not a big deal, but maybe something to think about for the next version of LÖVE.

I must have a slow computer (or graphics card)... didn't think that was the case, it was great when I bought it... I can certainly see a lag - if I grab the rectangle by the corner and then move it in that direction (the corner's direction) the mouse is outside the rectangle most of the time. In any...

There seems to be a small problem with having to poll to find the position of the mouse. For example, if I want to drag something (see file attached), then the object doesn't move together with the mouse. My suggestion is to have a mousemoved(x, y) callback to allow the application to deal with this...

After you shoot, set a counter (number of seconds to wait), and subtract dt in each call of update(dt).
When the counter is zero (or less than zero) you know that the time has passed and you can allow another shot.