Scratch

Thanks kayybee.

I guess it seems odd and rather exclusive being able to use the beta but not being able to provide feedback on it. At the very least, there could be a 2.0-specific topic in these forums so late-comers like me can actually contribute.

Here is my current 2.0 beta feedback, garnered from around a month's worth of scratch work with my daughter:

1. Bulk importing costumes results in the costumes being added in random order. This is incredibly painful when importing > 10 costumes as one must repeatedly drag costumes about until they're in the correct order. To make matters worse, you cannot drag them any further than the visible subset of costumes, so this results in a workflow of drag a bit, scroll, drag a bit, scroll, drag a bit, scroll, whoops - missed the scroll bar, scroll, drag a bit, aagh - I clicked delete!

2. Deleting a costume selects the previous costume instead of the next. If you delete the first costume, none are selected. This makes it time-consuming to delete a lot of costumes, because one must either delete, select, then delete again, OR one must select the lowest visible costume, delete it, then delete the one above it, then above that until you've deleted the top one, then go back down the list and repeat until they're all deleted.

3. The color picker is painful to use if the color in question comprises only a small part of the costume, or if the color isn't even on-screen at the moment because it's part of a costume that's hidden. Please, please, please make this easier. Perhaps provide a drop-down on the color picker that allows you to look through all costumes in all sprites, and permits zooming. Also, any chance the alpha channel could be included here?

4. What I wouldn't do for clone-scoped variables. They are absolutely crucial to sanely solving any number of problems. It was so difficult explaining to my daughter why we were doing all these hacks to get around this lack of feature. When I explained to her (she's 8) how we could do it if there were clone-scoped variables, she totally got it.

5. In the Data section, there's no visual distinction between variables of different scope. I think it would be helpful to group them visually into "Stage", "Sprite" and - when you add it    - "Clone" groups. I realize it makes no difference to the accessibility of the data, but it would make it clearer as to what you might be affecting by changing the variable, or what might affect you by accessing the variable.

6. Not sure if already addressed, but it would be nice if the new forums had markdown instead of this BBCode rubbish 

Thanks for passing on my feedback - I look forward to seeing it in the 2.0 forums and not being able to comment on any replies 

Kent

I really think 6 is an opinion, so I won't include it (as everyone will just say the same thing as this) but I'm actually really used to BBCode, along with most other people on this forum and almost all other forums (Bulletin Board Code is very widespread on forums)

Also 4. It's possible to make clone-specific variables. If you have a local variable, and you clone something, it becomes a clone-specific variable.

Here's the topic. Again, if you need to post something, just post it here.

2.  Opinions, opinions, opinions.  Those pesky opinions... 

That is all.

As for 5:

They'll add that.  1.4, if you're worked with it, they have it.  As for cloning, they're sprite variables.

^^last sentence sounded odd.