You can now (in v1.2.1) do
switch to costume (costume#) -1
Offline
kevin_karplus wrote:
You can now (in v1.2.1) do
switch to costume (costume#) -1
That is true, but I think that is better to there is <Previous costume> beacuse there is <Next costume>, and changing sprite costume will be easier.
Offline
Creating lots of new blocks for things that can be done fairly easily already is not going to help people learn the language or learn how to program well. New blocks should be used for things that are *hard* to do now or that make the language smaller and simpler to learn.
Sometimes there are difficult tradeoffs. Is 'next costume" worth keeping when
set costume to costume# +1
is easy? Probably, for the very beginner who is trying to do their very first animation, and is still struggling with the notion of getting the illusion of motion by changing costumes. But "previous costume" isn't needed by that beginner. By the time they are ready for "previous costume" they're probably ready for the more general and power concept of costume numbers.
Of course, some people will want shorthand ways to express things that they use a lot, which is why I like the idea of user-definable blocks. I would have no problem with a user defining "previous costume" and using it, if they found it helped them write code more easily.
Offline
FLUDD wrote:
http://scratch.mit.edu/projects/FLUDD/1406973
just use [blocks]<switch to costume[ (( <costume number-1> )) [/blocks]
Please do not move old threads (this one is from 2008) to the top of the forum when the issue has been resolved.
Thanks
Offline