It appears that the intersect function for "opaque pixels" is broken in
LiveCode Community. Can anyone confirm?
Thanks,
Roger
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your sub
Seems to work for me.
Tested with 2 buttons, the following script in 1 of them:
*on* mouseDown
*grab* me
*end* mouseDown
*on* mouseMove
*put* intersect(button 1,button 2, "opaque pixels")
*end* mouseMove
Moving the dragable button to the second button places true into the msg
box.
Ah but, create a non-opaque oval "ring", and a smaller opaque oval, "Dot" and
place the latter inside of the first
the intersect(Grc "Ring", Grc "Dot", "opaque pixels")
Should return false!
On Apr 12, 2013, at 6:59 PM, Mike Bonner wrote:
> Seems to work for me.
>
> Tested with 2 buttons, th
By golly, yep its broke.
On Fri, Apr 12, 2013 at 8:32 PM, Roger Guay wrote:
> Ah but, create a non-opaque oval "ring", and a smaller opaque oval, "Dot"
> and place the latter inside of the first
>
> the intersect(Grc "Ring", Grc "Dot", "opaque pixels")
>
> Should return false!
>
>
> On Apr 12,
Looks like its just doing the regular old bounds check. Intersecting rects
= true. Welp, with some other things going on, can't really move to
community yet. *sigh*
On Fri, Apr 12, 2013 at 8:51 PM, Mike Bonner wrote:
> By golly, yep its broke.
>
>
> On Fri, Apr 12, 2013 at 8:32 PM, Roger Guay
Bummer!!
On Apr 12, 2013, at 7:51 PM, Mike Bonner wrote:
> By golly, yep its broke.
>
>
> On Fri, Apr 12, 2013 at 8:32 PM, Roger Guay wrote:
>
>> Ah but, create a non-opaque oval "ring", and a smaller opaque oval, "Dot"
>> and place the latter inside of the first
>>
>> the intersect(Grc "R
Hi Roger et al.
We are aware of this bug and its in our quality control database-
http://quality.runrev.com/show_bug.cgi?id=10828
It should be fixed in the next release.
Kind Regards,
Neil Roger
--
RunRev Support Team ~ http://www.runrev.com
Support Open Source LiveCode on Kick-starter
http://
Thanks very much, Neil!
On Apr 13, 2013, at 2:43 AM, n...@runrev.com wrote:
> Hi Roger et al.
>
> We are aware of this bug and its in our quality control database-
>
> http://quality.runrev.com/show_bug.cgi?id=10828
>
> It should be fixed in the next release.
>
> Kind Regards,
>
> Neil Roge
