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.
Last edited by Jonathanpb (2009-12-02 04:08:32)
Offline
Yeah! Why not have previous costume anyway, when there's next costume? It just makes sense.
Offline
I know it's not neccessary, but neither is the "next costume" block.
After all, supposing they wouldn't include the Previous Costume block because it's not neccessary, why would they have added the Next Costume block anyway? If that was okay, why not get it done with?
I know it's not used as often as the Next Costume block, but it's still good for animating.
Offline
Personally I think we should just get rid of the next costume block.
We can always use
And ignore the minus block right above this text. That was an accident.
Last edited by cocoanut (2009-12-02 23:14:23)
Offline
This, and cocoanut's idea both work well. But of course for the people who don't know how to do that, I'd rather not do cocoanut's idea, and actually make the previous costume block. The reason they probably didn't do this was because in an animation, you don't usually go backwards.
Offline
Lucario621 wrote:
This, and cocoanut's idea both work well. But of course for the people who don't know how to do that, I'd rather not do cocoanut's idea, and actually make the previous costume block.
Yeah, that would be helpful. And it also saves time; I dislike having to reach in the areas just to get a simple piece going.
Lucario621 wrote:
The reason they probably didn't do this was because in an animation, you don't usually go backwards.
True... I was going to say that, but I didn't bother.
Offline
Lucario621 wrote:
This, and cocoanut's idea both work well. But of course for the people who don't know how to do that, I'd rather not do cocoanut's idea, and actually make the previous costume block. The reason they probably didn't do this was because in an animation, you don't usually go backwards.
Yes, in animations you're probably not going to go backwards, though sometimes, you might.
I don't know about getting rid of the next costume block... a lot of new Scratchers don't know how to get along without it.
Offline
Jonathanpb wrote:
I don't know about getting rid of the next costume block... a lot of new Scratchers don't know how to get along without it.
Not to mention that it would break a bunch of projects.
Offline
you can aslo use a variable
cause you can change that to a positive or negative number!
like <when green flag clicked>
<forever>
<switch to costume[ <{ <{costume }> }> ]
and then you will be able to freely change the costumes just by changing that variable,but it IS too much work for something simple like that!
Last edited by sonicx15 (2009-12-05 12:37:45)
Offline
However pointless (Next Costume) is, taking out blocks is making Scratch slightly worse.
Offline
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...
Offline
Good point! Take the comment feature included in Scratch 1.2 (which I have never used). I once downloaded a project, but there were comments, and you had to remove them all to play the game...
Offline
Why degrade when we can upgrade?
Offline
Yeah!
Offline
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...
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.
Last edited by hmnwilson (2009-12-06 01:07:23)
Offline
hmnwilson 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...
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. )
Offline
I think Scratch needs a previous costume block. For example, if you are making a game and in the game you gain a life, you might not be familar with <switch to costume[((costume <->1 )) . I'm not quite familiar with it myself.
Offline
Why is it that all my suggestions are getting bumped?
Anyway, I still want that block!
Offline
You can make this block.
BLOCK SPEC:
('previous costume' #- #previousCostume)
BLOCK CODING:
previousCostume self costumeIndex: self costumeIndex - 1
NOTE: replace the spaces with one TAB
You can just do that and then BAM, you have the previous costume block.
Offline