Remove the "Copy to new" button in the sound editor

0_009

There's a workaround:
1. Choose a sound from the sound library or upload a sound.
2. Copy and delete a piece of sound.
3. Upload another sound.
4. Select all of the newly uploaded sound and paste the stored up sound.

Zydrolic

just because there is a workaround does not mean its futile and should be thrown out the window

infact its much faster than your workaround

no support, this has no benefits.

-OdysseyCentral-

No support, the “Copy to new” button is much more accurate, there is much less sound ‘glitches’ than if you use the workaround

XCartooonX

Just because the button has a workaround doesn't mean it should be removed…

amogus1123

0_009 wrote:
There's a workaround:
1. Choose a sound from the sound library or upload a sound.
2. Copy and delete a piece of sound.
3. Upload another sound.
4. Select all of the newly uploaded sound and paste the stored up sound.

Some buttons exist for better quality. Workarounds aren't always needed.

mcsquaggle

no support. i know workaround but then again scratch team implements this:

next costume

when you can use this

switch costume to ((costume #) + (1))

they did this for convenience. so there wouldn't be any reason to remove something so good from the editor.

-Expo

Zydrolic wrote:
just because there is a workaround does not mean its futile and should be thrown out the window

infact its much faster than your workaround

no support, this has no benefits.

This is actually a very useful block for those who don't know/are learning coding.

Zydrolic

-Expo wrote:
(#7)
Zydrolic wrote:
just because there is a workaround does not mean its futile and should be thrown out the window

infact its much faster than your workaround

no support, this has no benefits.

This is actually a very useful block for those who don't know/are learning coding.

the sound editor has nothing to do with coding…

abcde26

No support. Since the workaround takes more time than just clicking a button, it makes the easy work harder. Please consider this quote:

If it ain't broke, don't fix it.

Means: if something is reasonably successful or effective, there is no need to change or replace it.

Thank you!

0_009

It should be removed because barely anyone uses it.

Zydrolic

0_009 wrote:
(#10)
It should be removed because barely anyone uses it.

Aaaaaand do you have even a singular peice of evidence to back that up?

Crispydogs101

0_009 wrote:
It should be removed because barely anyone uses it.

I actually use it a lot. It's a lot more useful than you think.
Also removing features in general does more harm than good.

amogus1123

Crispydogs101 wrote:
0_009 wrote:
It should be removed because barely anyone uses it.
I actually use it a lot. It's a lot more useful than you think.
Also removing features in general does more harm than good.

I use the feature to cut songs and check them with the original song e.g.
i can't see any supportation in this topic

stroyteller

No support, due to above reasons

mcsquaggle

0_009 wrote:
It should be removed because barely anyone uses it.

i use it, when i need to sync things. if i just play them next to eachother, the sound doesnt come out how i want so i use this button.

wilhelm43

Even with a workaround, why would you want to remove a function that's already been implemented ?

Zydrolic

wilhelm43 wrote:
(#16)
Even with a workaround, why would you want to remove a function that's already been implemented ?

0_009 wrote:
(#10)
It should be removed because barely anyone uses it.

then again he has
1. no evidence to back it up
2. is being proven wrong

medians

I didn't know this was a thing honestly:

What does it do exactly?
Edit: wait is it just duplicate
Edit 2: nvm i see

Last edited by medians (Oct. 23, 2023 13:06:31)

Zydrolic

medians wrote:
(#18)
-snip-

2.0 doesn't have it
3.0 does

cookieclickerer33

0_009 wrote:
It should be removed because barely anyone uses it.

when backdrop switches to [ v]

Discuss Scratch