[Beta3] Sphax VectorialLine

Hello again !
I'm proud to announce a new beta release of the VectorialLine object.

Additions :
- 3 new transformations (rotate, scale, translate) has been added. Some others will be added soon. Transformations are applied on points, not on the shape.
- New action "Set position from a point" to change the position of the entire line from a point of the line through a percentage (if you set the line to 100x20 from 50%, the line will be centered to 100x20)
- New action "Set Origin" for transformations (it allows you to apply a transformation to the line from a specific point. It's useful for rotations and scales)
- New expressions "Get rectangle Width" and "Get rectangle Height" to get the size of the line area.

Bugs corrected :
- Fine collision don't work if the line is hidden
- Small memory leak with fine collision detection
- Set line position don't work correctly (it has been renamed to "Set position from start")
- All float parameters was casted to int... Now all parameters like positions, thickness, dashs offset, etc are real float parameters for a real vectorial object.

Optimizations :
- If you don't want to have fine collision detection, you should deactivate the option, it will increase a (very little) bit the rendering of the line.
- Box collision has been a little bit optimized.

Examples :
- Vectorial Clock with smooth handles
- Vectorial invisible collisions
- VectorialLine basic example with collisions
- VectorialLine transformations

Known bugs :
- If transformations are made too early, they will not be applied. I think I can't do anything against this bug. You should apply transformations after one frame.

Soon :
- More expressions
- New transformations
- Your ideas if any

EDIT: I want to notice a little feature which is important for me : antialiasing. This feature for the VectorialLine object don't use the default one of MMF2 and is not cpu consuming. Use it !

Thanks a lot Novabrain.

Some other little features will coming soon but they will not be as powerful as the actual ones.

I'm pleased to see that my extension can open a lot of possibilities which can't be done before.

Some bugs have been discovered again, some of them have been corrected. The next beta is ready but, due to a MMF2 bug I've encountered (crash when an expression with parameter is called from a destroyed object) and a SDK limitation (it's impossible to test collisions from my object), the next beta will be delayed a bit.

With the next beta, you'll have a nice surprise too.

EDIT: I should notice you that all Sphax Vectorial objects are hardware accelerated (for the calculations, not the final renderer which is processed by MMF2). They will not be compatible with the future MMF2 HWA render option (but when this render mode will be available, I'll see what I can do for that ).