(distance to (x :: motion) (Y :: motion) :: sensing

Says the distance of the point X and Y. very usefull in interactive games or when you need to make some like appear

Mockups:

distance to (sprite v)//already in scratch

distance to x: () y: ()::sensing reporter

distance from x: () y: () to x: () y: ()::sensing reporter

Good idea, there is a workaround but that requires a extra sprite which can be annoying when you need a lot these. Support.

medians wrote:

Mockups:

distance to (sprite v)//already in scratch

distance to x: () y: ()::sensing reporter

distance from x: () y: () to x: () y: ()::sensing reporter

I dunno about the last block, cuz ST will just say "You can make it by using

< (Distance to x: (.10) y: (-10) :: sensing) < (Distance to x: (10) y: (10) :: sensing)>

I just realised I made wrong script

a boolean is a block that only returns true or false:

<this is what a boolean looks like>

i don't think you're suggesting this block to be a boolean, right?

ametrine_ wrote:

a boolean is a block that only returns true or false:

<this is what a boolean looks like>

i don't think you're suggesting this block to be a boolean, right?

Yes, I just wrote bolean so scratcher would look inside

Umhead22 wrote:

Yes, I just wrote bolean so scratcher would look inside

why not write “reporter” instead

ametrine_ wrote:

Umhead22 wrote:

Yes, I just wrote bolean so scratcher would look inside

why not write “reporter” instead

The title also should explain what the block is specifically. Reporter can mean a ton of stuff.

medians wrote:

(#2)
Mockups:

distance to (sprite v)//already in scratch

distance to x: () y: ()::sensing reporter

distance from x: () y: () to x: () y: ()::sensing reporter

Yeah i see the point. Its lot easier than using a sprite.

It's also a lot easier than the math workaround: (note how every coordinate has to appear twice)

([sqrt v] of ((((X1::custom-arg)-(x2::custom-arg))*((X1::custom-arg)-(x2::custom-arg)))+(((Y1::custom-arg)-(y2::custom-arg))*((Y1::custom-arg)-(y2::custom-arg)))))

vs

(distance from x:(X1::custom-arg) y:(Y1::custom-arg) to x:(x2::custom-arg) y:(y2::custom-arg)::sensing)

If the coordinates are stored in a list, the math workaround might not fit on the screen

([sqrt v] of ((((item (index1) of [coords v])-(item (index2) of [coords v]))*((item (index1) of [coords v])-(item (index2) of [coords v])))+(((item ((index1)+(1)) of [coords v])-(item ((index2)+(1)) of [coords v]))*((item ((index1)+(1)) of [coords v])-(item ((index2)+(1)) of [coords v])))))