Scratch
archived forums
#27 2010-11-21 16:38:51
Re: Previous costume
Jonathanpb wrote:
Since there's [next costume], why not have [previous costume]? Yes, I know you can do [switch to costume ((costume) - [1])], but it's just so simple, so why not? And it'd be nice and easy for animating and lives (you know, having the lives sprite go back a costume because of more health).
If you say that it isn't neccessary, delete the [next costume] block for the same reason.
I went into the system browser and made one. it is simple.
If you are reading this, please read to the end, because if you don't you won't know what's at the end. Don't just skip to the end though otherwise you won't be able to read the middle, which is most important. Now you must be wondering why you just read all that, the reason is you may have not noticed something, read it again and see if you notice it this time
Offline
#28 2010-11-21 20:15:58
Re: Previous costume
Pecola1 wrote:
Jonathanpb wrote:
Since there's [next costume], why not have [previous costume]? Yes, I know you can do [switch to costume ((costume) - [1])], but it's just so simple, so why not? And it'd be nice and easy for animating and lives (you know, having the lives sprite go back a costume because of more health).
If you say that it isn't neccessary, delete the [next costume] block for the same reason.I went into the system browser and made one. it is simple.
He knows that. But it still doesn't work online, and most Scratchers don't know how. Also note that this topic is a little old.
I still support though. 
Offline
#29 2010-11-24 17:31:18
Re: Previous costume
Chrischb wrote:
GirWaffles64 wrote:
However pointless (Next Costume) is, taking out blocks is making Scratch slightly worse.
Removing blocks may be a problem; I'm not entirely sure what it would do to projects that use the old blocks...
True, but scratch could make all those old Obsolete blocks turn into (for the next costume)
<switch to costume[ (( costume # <+> 1 ))
If you are reading this, please read to the end, because if you don't you won't know what's at the end. Don't just skip to the end though otherwise you won't be able to read the middle, which is most important. Now you must be wondering why you just read all that, the reason is you may have not noticed something, read it again and see if you notice it this time
Offline
#30 2010-11-24 21:57:34
Re: Previous costume
Pecola1 wrote:
Chrischb wrote:
GirWaffles64 wrote:
However pointless (Next Costume) is, taking out blocks is making Scratch slightly worse.
Removing blocks may be a problem; I'm not entirely sure what it would do to projects that use the old blocks...
True, but scratch could make all those old Obsolete blocks turn into (for the next costume)
[blocks]<switch to costume[ (( costume # <+> 1 ))[/blocks]
That's harder than it sounds. And as others have mentioned, not everyone knows how to do that.
Last edited by Harakou (2010-11-24 21:57:57)
Offline
#31 2010-11-26 14:32:20
Re: Previous costume
Harakou wrote:
Pecola1 wrote:
Chrischb wrote:
Removing blocks may be a problem; I'm not entirely sure what it would do to projects that use the old blocks...True, but scratch could make the next costume old Obsolete blocks turn into
[blocks]<switch to costume[ (( costume # <+> 1 ))[/blocks]That's harder than it sounds. And as others have mentioned, not everyone knows how to do that.
It may be hard. (this next part is going to confuse you) But really all they have to do is make in the system browser two places for the next costume block. One which changes the (possibly future) obsolete
<next costume>
block turn into the
[blocks]<switch to costume[ (( costume # <+> 1 ))[/blocks]
and the second would be just regular
Code:
nextCostume
self costumeIndex: self costumeIndex + 1If you are reading this, please read to the end, because if you don't you won't know what's at the end. Don't just skip to the end though otherwise you won't be able to read the middle, which is most important. Now you must be wondering why you just read all that, the reason is you may have not noticed something, read it again and see if you notice it this time
Offline
#32 2010-11-26 15:04:23
Re: Previous costume
Pecola1 wrote:
Harakou wrote:
Pecola1 wrote:
True, but scratch could make the next costume old Obsolete blocks turn into
[blocks]<switch to costume[ (( costume # <+> 1 ))[/blocks]That's harder than it sounds. And as others have mentioned, not everyone knows how to do that.
It may be hard. (this next part is going to confuse you) But really all they have to do is make in the system browser two places for the next costume block. One which changes the (possibly future) obsolete
<next costume>
block turn into the
[blocks]<switch to costume[ (( costume # <+> 1 ))[/blocks]
and the second would be just regularCode:
nextCostume self costumeIndex: self costumeIndex + 1
Yes, that is true, except:
1. The next version of Scratch won't be in Squeak.
2. That doesn't solve the problem that people new to Scratch will be confused, and miss out on an important block.
Offline
#33 2010-11-26 17:08:57
- Jonathanpb
- Scratcher
- Registered: 2008-07-25
- Posts: 1000+
Re: Previous costume
Meh meh meh let's just have the [previous costume] block.
"Human beings... must have action; and they will make it if they cannot find it.
-Charlotte Brontë
Offline
#35 2010-12-03 03:07:27
Re: Previous costume
Jonathanpb wrote:
hmnwilson wrote:
Chrischb wrote:
Removing blocks may be a problem; I'm not entirely sure what it would do to projects that use the old blocks...It wouldn't do anything. The scratch team has removed blocks before. They keep the code from the old blocks in later versions. So the old blocks work, they just turn red in the newer releases (comment block notwithstanding).
That doesn't mean I want the "next costume" block removed, though. Actually, the previous costume block is a good idea. I just thought I should point it out.
Ooh! (I and Chrischb came around in the days of Scratch 1.2.1, so we wouldn't know much.
I came in Scratch 1.1 (I think)
Hey. It's me SSSS, back from the dead!
Offline