rhinorulz wrote:
I have found the need for a goto block. what is your oppionion
Its ok... but as my dad tells me, its best to make your program in reuseable methods or functions, so you use the broadcast blocks.
Offline
What do you mean by go to?
not this, right?
Offline
I think rhinorulz is talking about "go to [ ]" with lines of code - it would move the acting spot in the script to the specified spot.
I don't like the idea... I think it's better to just build your script the normal way.
Offline
markyparky56 wrote:
rhinorulz wrote:
I have found the need for a goto block. what is your oppionion
Its ok... but as my dad tells me, its best to make your program in reuseable methods or functions, so you use the broadcast blocks.
Yes, when I need to do something like this I split the script into different "When I Receive" scripts, like this:
[blocks]<when green flag clicked>
[do stuff]
<broadcast[ password
<when I receive[ password
ask [Enter your password, please] and wait
<if><( answer <=> <{ pass }> )>
<broadcast[ log in
<else>
<say[ Wrong password. ]for( 2 )secs>
<broadcast[ password
<end>[/blocks]
But broadcasts will slow down the project. Because of that and to save broadcasts it'd be nice if you would mark sections of a script with a block and use goto to go to that section. I'll make a mockup now
EDIT: Done:
Last edited by technoguyx (2010-04-25 21:12:19)
Offline
Can't you make the same thing with a "forever if" loop?
Goto is, today, seen as bad practice in most languages, some doesn't even implement it.
I doubt Scratch team will introduce something teaching bad programming habits... :-)
It would be better to have efficient broadcast (if it is so laggy) or custom blocks or similar solutions.
Offline
Phi_Lho wrote:
Can't you make the same thing with a "forever if" loop?
Goto is, today, seen as bad practice in most languages, some doesn't even implement it.
I doubt Scratch team will introduce something teaching bad programming habits... :-)
It would be better to have efficient broadcast (if it is so laggy) or custom blocks or similar solutions.
do you play any online game on the pc?
Offline
weaverman wrote:
Phi_Lho wrote:
Can't you make the same thing with a "forever if" loop?
Goto is, today, seen as bad practice in most languages, some doesn't even implement it.
I doubt Scratch team will introduce something teaching bad programming habits... :-)
It would be better to have efficient broadcast (if it is so laggy) or custom blocks or similar solutions.do you play any online game on the pc?
Hey there, weaverman, I think it would be a better idea if you started your own topic about online gaming (preferably in the 'Miscellaneous' forums) rather than try to change the topic in an already existing thread.
Offline
technoguyx wrote:
But broadcasts will slow down the project. Because of that and to save broadcasts it'd be nice if you would mark sections of a script with a block and use goto to go to that section. I'll make a mockup now
EDIT: Done:
I really like that idea! But... maybe something a bit more like it being a container block.
Mockup:
Last edited by markyparky56 (2010-04-26 11:15:27)
Offline
markyparky56 wrote:
technoguyx wrote:
But broadcasts will slow down the project. Because of that and to save broadcasts it'd be nice if you would mark sections of a script with a block and use goto to go to that section. I'll make a mockup now
EDIT: Done:
http://img36.imageshack.us/img36/1254/gotomock.gifI really like that idea! But... maybe something a bit more like it being a container block. (Mockup coming soon)
Hmmm, maybe
Offline
technoguyx wrote:
markyparky56 wrote:
technoguyx wrote:
But broadcasts will slow down the project. Because of that and to save broadcasts it'd be nice if you would mark sections of a script with a block and use goto to go to that section. I'll make a mockup now
EDIT: Done:
http://img36.imageshack.us/img36/1254/gotomock.gifI really like that idea! But... maybe something a bit more like it being a container block. (Mockup coming soon)
Hmmm, maybe
That way, it would be able to just act like real programming languages, which go to that area, then jump back. Because your version would ust jump to there, and work its way back down again. Thats ok for what your scrpt was like, but for some other types it would be harder and not as easy to intergrate.
Offline
Actualy... iv got a better idea, plus removes the chance of spelling mistakes.
Offline
@marky
Lol@your font
Offline