Allow to set any movement to the camera

[christopho]

For now, the only camera movement is moving toward a point and getting back to the hero. This is not flexible and makes it hard to do nice cutscenes.
It would be better to accept any movement object for the camera.

[wrightmat]

This could work by changing the x, y parameters to object_to_move (which could optionally be an x,y table like with movement:start) and adding a return true/false in the callback to indicate whether to return to the hero or not. If nothing is declared it could default to return true and go back to the hero (thereby not breaking any previous code), but if you declare return false the camera would stay at that point (or follow it in the case of a moving object) until move_camera is called again.

[ekureina]

Absolutely. Also, there could also be a function for movement in a polygon and/or an arc.

[christopho]

The camera will simply be an entity in 1.5. This gives the whole entity API including movements and collisions, for free.

[christopho]

Done