Scratch

throughthefire · 2010-03-22 19:46:03

I was trying to create a board game on scratch, and for ease of programming, I wanted to make the costume names of the various numbers of the dice the actual numbers (the dice with the one on it would be named 1, so on and so forth). However, I noticed that the costume naming thing HAD to put a 1 at the end of it, making my idea seem less practical. Please get rid of the automatic costume thingamajigy in the next version of scratch!

hmnwilson · 2010-03-22 19:53:10

IIRC it didn't exist until 1.3... before that naming costumes was much less annoying.

Chrischb · 2010-03-22 20:14:42

I definitely agree! mad

steppenwulf · 2010-03-22 20:21:34

I support this post!

Chrischb · 2010-03-22 20:22:34

Let's bump it until someone notices. big_smile

Jonathanpb · 2010-03-23 01:31:01

It's so irritating! mad

When I work on my Star Wars sprites (for my collection big_smile ), it takes quite a while to fix costume numbers... neutral

Vista4563 · 2010-03-23 01:43:01

Agreed. Even though Scratch's "auto numbering" is a mechanism to prevent duplicate sprite names, it can be really annoying.

Bopitman99 · 2010-03-23 02:51:32

You could name them 'one', 'two' etc...

But still, I really want them to change this, it gets so annoying neutral

Greenboi · 2010-03-23 11:32:34

Sometime it's helpful, but most times it's just a plain hassle to deal with, and sometimes impossible to fix. mad

markyparky56 · 2010-03-23 11:51:33

helpful sometimes, but annoying even more.

Lightnin · 2010-03-23 15:13:15

Ah - I'm pretty sure this will get solved when we release Scratch 2.0, since it will be implemented in different code. I can't swear to it - but you'll probably get your wish!

nXIII · 2010-03-23 15:13:21

Just use costumes named something like '1dice', '2dice', '3dice', etc. and use a
[blocks]<switch to costume[(( join ((<{ number }>))(( dice ))[/blocks]

Sorry, it's a bit messy because [blocks ] doesn't support join...

Last edited by nXIII (2010-03-23 15:15:46)

Chrischb · 2010-03-23 17:46:02

Lightnin wrote:
Ah - I'm pretty sure this will get solved when we release Scratch 2.0, since it will be implemented in different code. I can't swear to it - but you'll probably get your wish!

Hooray!
Thanks for the feedback, Lightnin. smile

Jonathanpb · 2010-03-23 17:52:43

Lightnin wrote:
Ah - I'm pretty sure this will get solved when we release Scratch 2.0, since it will be implemented in different code. I can't swear to it - but you'll probably get your wish!

Yay! Yay! Yay! big_smile

smile

steppenwulf · 2010-03-23 18:05:38

Lightnin wrote:
Ah - I'm pretty sure this will get solved when we release Scratch 2.0, since it will be implemented in different code. I can't swear to it - but you'll probably get your wish!

big_smile

markyparky56 · 2010-03-24 12:19:16

nXIII wrote:
Just use costumes named something like '1dice', '2dice', '3dice', etc. and use a
[blocks]<switch to costume[(( join ((<{ number }>))(( dice ))[/blocks]

Sorry, it's a bit messy because [blocks ] doesn't support join...

That what you mean?

hmnwilson · 2010-03-24 12:32:50

nXIII wrote:
Just use costumes named something like '1dice', '2dice', '3dice', etc. and use a
[blocks]<switch to costume[(( join ((<{ number }>))(( dice ))[/blocks]

Sorry, it's a bit messy because [blocks ] doesn't support join...

That won't work... when you put a reporter into the "switch to costume" block, it only checks for numbers and switches to that costume number. (wait, that might be the solution to throughthefire's problem!)

But I still definitely support the removal of the automatic numbering. It causes a lot of problems when trying to rename costumes.

Last edited by hmnwilson (2010-03-24 12:33:33)

markyparky56 · 2010-03-24 13:02:52

hmnwilson wrote:
nXIII wrote:
Just use costumes named something like '1dice', '2dice', '3dice', etc. and use a
[blocks]<switch to costume[(( join ((<{ number }>))(( dice ))[/blocks]

Sorry, it's a bit messy because [blocks ] doesn't support join...
That won't work... when you put a reporter into the "switch to costume" block, it only checks for numbers and switches to that costume number. (wait, that might be the solution to throughthefire's problem!)

But I still definitely support the removal of the automatic numbering. It causes a lot of problems when trying to rename costumes.

It does work. I just checked it.

illusionist · 2010-03-24 13:16:22

I agree, and Scratch Team must see. smile

nXIII · 2010-03-24 17:37:16

hmnwilson wrote:
nXIII wrote:
Just use costumes named something like '1dice', '2dice', '3dice', etc. and use a
[blocks]<switch to costume[(( join ((<{ number }>))(( dice ))[/blocks]

Sorry, it's a bit messy because [blocks ] doesn't support join...
That won't work... when you put a reporter into the "switch to costume" block, it only checks for numbers and switches to that costume number. (wait, that might be the solution to throughthefire's problem!)

But I still definitely support the removal of the automatic numbering. It causes a lot of problems when trying to rename costumes.

Wrong, wrong, wrong-o! You are WRONG! It takes the string and checks through the costumes. Take, for example, like EVERY SINGLE ONE of my projects...

Last edited by nXIII (2010-03-24 17:40:41)

hmnwilson · 2010-03-24 20:57:14

nXIII wrote:
hmnwilson wrote:
nXIII wrote:
Just use costumes named something like '1dice', '2dice', '3dice', etc. and use a
[blocks]<switch to costume[(( join ((<{ number }>))(( dice ))[/blocks]

Sorry, it's a bit messy because [blocks ] doesn't support join...
That won't work... when you put a reporter into the "switch to costume" block, it only checks for numbers and switches to that costume number. (wait, that might be the solution to throughthefire's problem!)

But I still definitely support the removal of the automatic numbering. It causes a lot of problems when trying to rename costumes.
Wrong, wrong, wrong-o! You are WRONG! It takes the string and checks through the costumes. Take, for example, like EVERY SINGLE ONE of my projects...

Seriously? For me it doesn't do anything at all. I even tried the script you made... nothing happened. (and yes, the costumes were named correctly.)

Last edited by hmnwilson (2010-03-24 20:58:22)

nXIII · 2010-03-24 20:58:52

hmnwilson wrote:
nXIII wrote:
hmnwilson wrote:

That won't work... when you put a reporter into the "switch to costume" block, it only checks for numbers and switches to that costume number. (wait, that might be the solution to throughthefire's problem!)

But I still definitely support the removal of the automatic numbering. It causes a lot of problems when trying to rename costumes.
Wrong, wrong, wrong-o! You are WRONG! It takes the string and checks through the costumes. Take, for example, like EVERY SINGLE ONE of my projects...
Seriously? For me it doesn't do anything. I even tried the script you made... nothing happened at all. (and yes, the costumes were named correctly.)

Um... is that like a beta-ish version or something?

Jonathanpb · 2010-03-25 00:40:46

When you put a reporter into the [switch to costume [costume1]] block, it'll only change costume if the costume has a number name. The name "13" would work, but not "costume13".

fg123 · 2010-03-25 00:54:33

Really? I didn't know that...

Jonathanpb · 2010-03-25 01:00:50

I didn't know either! I just tested it for the post! tongue

Scratch

archived forums

#1 2010-03-22 19:46:03

costume naming

#2 2010-03-22 19:53:10

Re: costume naming

#3 2010-03-22 20:14:42

Re: costume naming

#4 2010-03-22 20:21:34

Re: costume naming

#5 2010-03-22 20:22:34

Re: costume naming

#6 2010-03-23 01:31:01

Re: costume naming

#7 2010-03-23 01:43:01

Re: costume naming

#8 2010-03-23 02:51:32

Re: costume naming

#9 2010-03-23 11:32:34

Re: costume naming

#10 2010-03-23 11:51:33

Re: costume naming

#11 2010-03-23 15:13:15

Re: costume naming

#12 2010-03-23 15:13:21

Re: costume naming

#13 2010-03-23 17:46:02

Re: costume naming

Lightnin wrote:

#14 2010-03-23 17:52:43

Re: costume naming

Lightnin wrote:

#15 2010-03-23 18:05:38

Re: costume naming

Lightnin wrote:

#16 2010-03-24 12:19:16

Re: costume naming

nXIII wrote:

#17 2010-03-24 12:32:50

Re: costume naming

nXIII wrote:

#18 2010-03-24 13:02:52

Re: costume naming

hmnwilson wrote:

nXIII wrote:

#19 2010-03-24 13:16:22

Re: costume naming

#20 2010-03-24 17:37:16

Re: costume naming

hmnwilson wrote:

nXIII wrote:

#21 2010-03-24 20:57:14

Re: costume naming

nXIII wrote:

hmnwilson wrote:

nXIII wrote:

#22 2010-03-24 20:58:52

Re: costume naming

hmnwilson wrote:

nXIII wrote:

hmnwilson wrote:

#23 2010-03-25 00:40:46

Re: costume naming

#24 2010-03-25 00:54:33

Re: costume naming

#25 2010-03-25 01:00:50

Re: costume naming

Board footer