edit: stop posting here (I reported it to be closed)

So, we all know what this block is and what it does, right? It’s kind of self-explanatory
in case you don’t know what it looks like here it is why doesn’t the forums have this block, I have to screeshot it now

and it makes things EXTREMELY easy, it could be worked around like this if you really needed it

when green flag clicked
forever
if <<mouse down?> and <touching [ mouse pointer] ?>> then
go to [ mouse pointer]
end
end

edit: I’m sorry if this is a dupe, I didn’t check for duplicates

But the workaround doesn't completely work if you move your mouse quick enough.

Aside from that, I would put this under the category of “It exists, and it's not causing any problems, so why remove it?”

Za-Chary wrote:

But the workaround doesn't completely work if you move your mouse quick enough.

Aside from that, I would put this under the category of “It exists, and it's not causing any problems, so why remove it?”

isn’t this site about coding? it wouldn’t make sense if it has a block that could solve all of the person’s problems, I think it’s better for users to figure it out

CoolLionMan wrote:

Za-Chary wrote:

But the workaround doesn't completely work if you move your mouse quick enough.

Aside from that, I would put this under the category of “It exists, and it's not causing any problems, so why remove it?”

isn’t this site about coding? it wouldn’t make sense if it has a block that could solve all of the person’s problems, I think it’s better for users to figure it out

And? At least 90% of Scratch blocks are workaroundable. Also, drag mode has been around for a long time. The workaround also doesn't feel nearly as nice as the features does, too; clicking on a sprite will snap the center to your current mouse position instead of having you pick it up in a reasonable way, if you hold your mouse down and run it into a sprite it will still pick it up, and I'm pretty sure you can accidentally drag multiple objects at once like this. No support.

The workaround you have provided is not sufficient and while there is a complete workaround it's not fun to use, and the removal of it would break some projects.

Yes, it is a coding website where you learn to code. However, it's fine if some of the blocks are workaroundable. We might as well teach kids machine code, if you insist that no workaroundable blocks exist.
Also, many blocks do happen to be workaroundable so why single this one out?

I like the block. To fully recreate it would be a rather long script.

There is no benefit for everyone if the block was removed entirely.

edit: Also, workarounds can't be used for everything, as a new scratcher will not know the workaround with complex variables.

CoolLionMan wrote:

when green flag clicked
forever
if <<mouse down?> and <touching [ mouse pointer] ?>> then
go to [ mouse pointer]
end
end

This is the real workaround that behaves the same way as the block:

when green flag clicked
forever
wait until <<mouse down?> and <touching [mouse pointer v]?>>
set [dx v] to ((x position) - (mouse x))
set [dy v] to ((y position) - (mouse y))
repeat until <not <mouse down?>>
go to x: ((mouse x) + (dx)) y: ((mouse y) + (dy))

It's actually quite complex, especially for a beginner, so I don't think the block should be removed.

No remove set drag mode draggable
It will be hard for beginners.

Maximouse wrote:

CoolLionMan wrote:

when green flag clicked
forever
if <<mouse down?> and <touching [ mouse pointer] ?>> then
go to [ mouse pointer]
end
end

This is the real workaround that behaves the same way as the block:

when green flag clicked
forever
wait until <<mouse down?> and <touching [mouse pointer v]?>>
set [dx v] to ((x position) - (mouse x))
set [dy v] to ((y position) - (mouse y))
repeat until <not <mouse down?>>
go to x: ((mouse x) + (dx)) y: ((mouse y) + (dy))

It's actually quite complex, especially for a beginner, so I don't think the block should be removed.

No support.

Maximouse wrote:

This is the real workaround that behaves the same way as the block:

when green flag clicked
forever
wait until <<mouse down?> and <touching [mouse pointer v]?>>
set [dx v] to ((x position) - (mouse x))
set [dy v] to ((y position) - (mouse y))
repeat until <not <mouse down?>>
go to x: ((mouse x) + (dx)) y: ((mouse y) + (dy))

It's actually quite complex, especially for a beginner, so I don't think the block should be removed.

Still not perfect. Here's the perfect script:

when green flag clicked
forever
wait until <<(click) = (1)> and <touching [mouse pointer v]?>>
set [dx v] to ((x position) - (mouse x))
set [dy v] to ((y position) - (mouse y))
repeat until <not <mouse down?>>
go to x: ((mouse x) + (dx)) y: ((mouse y) + (dy))
end
when green flag clicked
forever
set [click v] to (0)
wait until <not <mouse down?>>
wait until <mouse down?>
set [click v] to (1)
end

I think we can all agree it's a pretty simple and convenient workaround

Edit: Turns out I got it wrong on the first try. That's probably because it was so simple that I made a mistake

No support. The Whys:
1.

dertermenter wrote:

There is no benefit for everyone if the block was removed entirely.

edit: Also, workarounds can't be used for everything, as a new scratcher will not know the workaround with complex variables.

2.

-EmeraldThunder- wrote:

I like the block. To fully recreate it would be a rather long script.

3.

gosoccerboy5 wrote:

The workaround you have provided is not sufficient and while there is a complete workaround it's not fun to use, and the removal of it would break some projects.

Yes, it is a coding website where you learn to code. However, it's fine if some of the blocks are workaroundable. We might as well teach kids machine code, if you insist that no workaroundable blocks exist.
Also, many blocks do happen to be workaroundable so why single this one out?

4.

Za-Chary wrote:

But the workaround doesn't completely work if you move your mouse quick enough.

Aside from that, I would put this under the category of “It exists, and it's not causing any problems, so why remove it?”

Rendangbike2 wrote:

No support. The Whys:
1.

dertermenter wrote:

There is no benefit for everyone if the block was removed entirely.

edit: Also, workarounds can't be used for everything, as a new scratcher will not know the workaround with complex variables.

2.

-EmeraldThunder- wrote:

I like the block. To fully recreate it would be a rather long script.

3.

gosoccerboy5 wrote:

The workaround you have provided is not sufficient and while there is a complete workaround it's not fun to use, and the removal of it would break some projects.

Yes, it is a coding website where you learn to code. However, it's fine if some of the blocks are workaroundable. We might as well teach kids machine code, if you insist that no workaroundable blocks exist.
Also, many blocks do happen to be workaroundable so why single this one out?

4.

Za-Chary wrote:

But the workaround doesn't completely work if you move your mouse quick enough.

Aside from that, I would put this under the category of “It exists, and it's not causing any problems, so why remove it?”

couldn't have said it better myself.
some person: it's workaroundable, so we don't need it.
response: why do we have

next costume
next backdrop
change [ v] by ()
change x by ()
change y by ()
() + ()
() * ()

?
answer:

gosoccerboy5 wrote:

Yes, it is a coding website where you learn to code. However, it's fine if some of the blocks are workaroundable. We might as well teach kids machine code, if you insist that no workaroundable blocks exist.

Hearst10 wrote:

snip

Please snip your post like this!

no support.
most blocks have a workaround.
for example you could workaround

move (10) steps

by using

go to x: ((x position) + (([sin v] of (direction)) * (10))) y: ((y position) + (([cos v] of (direction)) * (10)))

so basically the move 10 steps block is useless but i wouldnt say it should be removed

Robby_Blue wrote:

no support.
most blocks have a workaround.
for example you could workaround

move (10) steps

by using

go to x: ((x position) + (([sin v] of (direction)) * (10))) y: ((y position) + (([cos v] of (direction)) * (10)))

so basically the move 10 steps block is useless but i wouldnt say it should be removed

Did you get that from the Scratch Wiki?

Anyways, no support. Using that workaround doesn't really work if you drag it to fast. Also, beginners might not know this workaround.

GoogleInScratch wrote:

beginners might not know this workaround.

I agree with this ^

It's been 24 hours since the topic was created, there should be a Close Topic button under the Submit button.