Indeed, I won't list them but I get at least 5 use cases popping into my head
the moment I saw this, where one would want the intersection between 1 object
and an invisible object 2:
just one: solution to a puzzle could be invisible. as user moves tiles around
the intersect would trigger "got it" for placement. In fact I am using
another algorithm for this very use case where we do stuff like store the loc
of the hidden object then on mouse drag check the abs of the loc of the dragged
vsibiel object …. and I'm thinking think, sheesh… I thinking I could be
using intersect instead…
is intersect expensive on mobile? Performant on Android?
BR
On 7/14/17, 1:11 AM, "use-livecode on behalf of Mark Waddingham via
use-livecode" <use-livecode-boun...@lists.runrev.com on behalf of
use-livecode@lists.runrev.com> wrote:
As Lagi pointed out one can imagine that there are use-cases where you
want to know whether two things intersect regardless of whether they can
be seen (i.e. visible false, or blendLevel 100). Indeed, I don't recall
anyone ever commenting on this - so either it was too long ago and I
have since forgotten, or it is useful the way it currently is.
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
