fdreerf

TL;DR: prevent precarious problematic purges of sprites by making the delete sprite button not exist or smaller


This suggestion exists as a safeguard to prevent accidental sprite deletions. And while it is a good suggestion, I think it would be better to remove the source of these accidents, instead of simply creating a pop-up.





This. This immense, ginormous button, is what I consider the most likely source for these accidents. The delete sprite button is fairly pointless. Why must there be a giant button for the act of deleting a sprite? It might as well be for duplicating a sprite or exporting a sprite, and unlike deleting the sprite, those don't cause potentially hours of work lost. Deleting a sprite is an uncommon action; I only use it to get rid of the default Cat, but it wouldn't take much longer to right-click it and then delete it that way. Plus, it's harder to accidentally delete the sprite through the dropdown menu.

Take this scenario where you have quite a large number of sprites.



You're in the swing of things, the zone as they call it, completely focused on finishing your project, and working very quickly. You finished what you need to do in the Giga sprite and need to work on either Gobo, Nano, or the Cheesy Puffs. Because of the size of the button, you can potentially click on the massive delete button and lose not only the hours of work in the sprite, but the hours of potential work that now is lost from re-creating the sprite and as well as losing your focus. This is also exasperating when using the small stage option, as the sprites are either in one or two columns, which makes the likelihood of clicking delete greater.

Normally I would say to be more careful when these types of things appear in the forums, but it is a real problem that can be solved with one simple fix: make the button smaller. There is no need for deleting a sprite to be so easy where accidents are more of a probability than a possibility. Of course, there are some users who may not be able to right-click for whatever reason, so for that reason, I say to make the button smaller. The button's size does need to be around 44% of the length of the sprite box!


this is the third revision of this image so you better like it


Though I would like it for the button to be removed completely, a smaller button would solve the problem nicely. Take, for instance, the Scratch GUI delete button, which is much smaller, though still easy to purposefully press on mobile devices.



Notice how the button doesn't hang over the edges of the sprite icon. Even if it's pretty small, I'd still think that if the button is still present, that this suggestion should also go in tandem with the one linked above. Overall, doing this will make accidents far less likely, and it's a really simple fix.

Mr_PenguinAlex

Support, there is literally no reason for it to be so big or even be there when you can right click.

misteray

Absolute support, and its coming from fdreef, so I don't have to live with that I'm supporting a dupe because I didn't search up the right thing

-CloudGate-

not remove it just make it smaller, because of mobile

fdreerf

-CloudGate- wrote:

not remove it just make it smaller, because of mobile
I thought long-pressing acted as a right-click on mobile. I hadn't really thought about mobile but you really shouldn't use the Scratch online editor on mobile; that's just dreadful.

krattgirl20

fdreerf wrote:

-CloudGate- wrote:

not remove it just make it smaller, because of mobile
I thought long-pressing acted as a right-click on mobile. I hadn't really thought about mobile but you really shouldn't use the Scratch online editor on mobile; that's just dreadful.
yeah, mobile scratch is soooo hard

lm1996

Support, I've never had this happen, but I'm sure it'll come up sooner or later enough.

Skywarslord

I'm fully for this, the exact scenario happened to me yesterday and I wouldn't want the same to happen to others.

LengendaryBunny

This is a good idea, the overly enlarged button can get in the way sometimes. I've accidentally deleted a sprite too many times to count thanks to that button.

sportfan999

This is super smart. Can't believe this hasn't been suggested yet. Support!

Ihatr

This thing is bigger than it should be. I'd rather have it be shrunken a bit, because you can't actually hold-click to use the right-click menu on mobile. So, I'd like it to be about 3 quarters of the current size, so 105 px in diameter. I think that would be good enough

IndianRuby718

Yes, please make the button smaller! I would also say to make the even more ginormous new sprite button waaaay smaller and move it to the corner so it takes as much space as the delete button, or make it similar to the add extensions button, because we can barely select the sprites on the row it covers, but that's off topic

fdreerf

IndianRuby718 wrote:

because we can barely select the sprites on the row it covers, but that's off topic
???
No, it isn't offtopic, it's a great point on why the button should be smaller and I'll add it to the OP.

OffShock

No support, due to the edit button in the top right corner of your screen having an undo last delete button that works sprites, code and backdrops. No need for it unless you delete multiple sprites and that's probably on purpose rather then on accident.

fdreerf

OffShock wrote:

No support, due to the edit button in the top right corner of your screen having an undo last delete button that works sprites, code and backdrops. No need for it unless you delete multiple sprites and that's probably on purpose rather then on accident.
That button is not very well know about and doesn't even work half the time. Plus, reducing the accident in the first place is a much better solution in the long-term.

OffShock

fdreerf wrote:

OffShock wrote:

No support, due to the edit button in the top right corner of your screen having an undo last delete button that works sprites, code and backdrops. No need for it unless you delete multiple sprites and that's probably on purpose rather then on accident.
That button is not very well know about and doesn't even work half the time. Plus, reducing the accident in the first place is a much better solution in the long-term.

I've found that it works all the time for me, I don't know if I'm lucky or something but I think it's fine. Also aren't the point of suggestion forums other then adding in features is finding ways to work around said suggestion? ( I remember a thread when someone wanted a pause/play sound button but somebody found a work around. Wouldn't this fall under the same category?) If so then a suggestion solving a problem that's already been solved seems redundant.

IndianRuby718

fdreerf wrote:

IndianRuby718 wrote:

because we can barely select the sprites on the row it covers, but that's off topic
???
No, it isn't offtopic, it's a great point on why the button should be smaller and I'll add it to the OP.
Well that's about the new sprite button, not the delete button… so that should be off-topic, right?

OffShock wrote:

[snip] Also aren't the point of suggestion forums other then adding in features is finding ways to work around said suggestion? ( I remember a thread when someone wanted a pause/play sound button but somebody found a work around. Wouldn't this fall under the same category?) If so then a suggestion solving a problem that's already been solved seems redundant.
Yes, workarounds for code, not workarounds for making the interface easier to use. Also, not everything should be rejected just for a workaround. It depends on how practical having a new block or other feature is compared to the workaround.

fdreerf

OffShock wrote:

Also aren't the point of suggestion forums other then adding in features is finding ways to work around said suggestion? ( I remember a thread when someone wanted a pause/play sound button but somebody found a work around. Wouldn't this fall under the same category?) If so then a suggestion solving a problem that's already been solved seems redundant.
No, the point of the suggestions forums is not to find workarounds as every suggestion would be closed for having one. The Restore button is not a workaround, let alone a good one, as my suggestion prevents accidental deletions in the first place. You could use the Restore that most people have no clue about its existence and is very faulty, or you could just be far less likely to delete it, avoiding the situation entirely. It is much more practical to prevent a problem than to solve it after it has happened. You can put rescue stations at the bottom of steep hills and canyons for when cars fall off of them, or you can just place guard rails on those steep roads so there are fewer crashes.

IndianRuby718 wrote:

Well that's about the new sprite button, not the delete button… so that should be off-topic, right?
Oh, you were talking about that. I didn't notice.

OffShock


I haven't found the restore button to be faulty, when I'm using it it restores the sprite or backdrop and the code with it and it hasn't failed me yet.
Also with your example if you delete a sprite it take 2 clicks to get it back, that's like 2 seconds, which I feel like isn't big enough of a problem to offer a better solution. I guess it would be a big problem if the restore button was faulty but it's not. (At least for me) Also the ST has plenty of other things to do that have a much bigger effect then 2 seconds shaved off a project, like fix mass reporting and the reshare bug.


fdreerf

OffShock wrote:

Also the ST has plenty of other things to do that have a much bigger effect then 2 seconds shaved off a project, like fix mass reporting and the reshare bug.
Those aren't problems, those are kids whining because somebody else got bigger number than themselves because of untimely circumstances.

And again, not everybody knows about the Restore button! If somebody that didn't know were to leave the project page to try and find help, the restore button would simply not do anything as it would not be able to be clicked. If the page refreshes or you leave it will do nothing, which is a huge problem.

My example said nothing about the speed of recovering the sprite, I was just simply saying that if you're working fast accidents are prone to happen.