corona
corona copied to clipboard
coronalabs
Boundary checking
As requested, leaving this here.
To give developers more control of what Solar does automatically, I propose to be able to toggle things like automatic boundary checking.
It's possible I did something along these lines in this PR (with less robust attempts in its predecessors).
Some of my tests involved 3D meshes and the culling was fighting that.
This involved display.getDefault() / display.setDefault(), so you enabled cull / hit test settings and then did display.new*().
The following is more of less the implementation. It was part of something much larger, so it's very possible I've missed something.
Getters / Setters for defaults, with declarations further down. Constructor for defaults.
getDefault and setDefault for those keys.
Property flags for display objects.
Binding the keys to those properties on object creation.
Extra "we can't get here", I think? Been a while since I wrote this. 😄
Preparing a group and updating its transform.
Added CanHitTest() with default implementation, and accounting for it in hit events. (EDIT: CanHitTest() was important to what the PRs were trying to achieve, but the "skip hit tests" flag doesn't rely on it.)
So give me the simple answer.... Is this in Solar already or does it need implementation?
It's not available already, no. PRs still pending.
Maybe I can throw together a build next week and let you give it a test.