this is tripped out

[Shyfire]

i made this by mistake but it cool none the less

[ssr]

um flashy! 8)

[Cervantes]

There's no need to post stuff like that, especially because it uses processes.

[MiX-MaztA-M8riX]

OMFG SHANE!
STOP STEALING MY STUF

It even says on the button bar up there, 'By : Martin Borowiec'

holy christ, oh well hez a N00bz0r, I'll let him have this one

[[Gandalf]]

I was too busy turning my head away to look at the button bar

[Shyfire]

all i did was copy and past the set screen its not ur proggy i just couldnt remeber how to setscreen

[cool dude]

that hurts my eyes! pretty good although processes are evil and don't use them

[endusto]

whats wrong with processes?

[Cervantes]

they suck

[Flikerator]

Cervantes wrote:

they suck

That was pretty good lolz. They do suck, they make everything slow and not cool. You want to be not cool? Thats whay I thought.

[[Gandalf]]

wait... so this means that procedures are good, right?

while I'm at it, can someone breifly explain the difference between how processes and procedures work?

[Flikerator]

[Gandalf] wrote:

wait... so this means that procedures are good, right?

while I'm at it, can someone breifly explain the difference between how processes and procedures work?

Yah sure. With a process you have to fork it. That means that when its forked the code will run, and you can continue with other things. So I can have a ball moving and a 4 paddles moving all at the same time. You can do that with just a loop but in reality they arn't being done at the same time, but it looks like it. You used to have to use that for music. Because if you just played music then it would play out before the other code could play. Its been solved in the new version with Music.PlayFileLoop I think.

Anyways...

With a procedure you write all the code you want in it. Usually you do it witb something that you are going to call more then once but you cannot loop it. It cuts down on the number of code. They are very helpful to make your code shorter and more efficient. I don't use them enough but anyways.... An example would be drawing a little dude. If he is more then just an oval it may be helpful to create him earlier and call him later when you need him. So if he is 20 lines of code you don't have to keep rewriting them everytime you have a cutscene..

Not a very good example but if you need a better one I can look up one up in my files.

[lapo3399]

lol sum1 already posted

[lapo3399]

Procedure: Specific piece of code that can be called upon by entering its name. Used for repetition.
e.g. This would say hello (run the procedure) three times

code:

procedure hello put "Hello!!" end hello hello hello hello

Process: Specific piece of code that is supposed to run while other parts of the program are running. I do not recommend using them because this is not really the case, and processes in turing are squirrelly.

Now you know. Next time maybe you should ask on a help forum/topic.

[Flikerator]

lapo3399 wrote:

Procedure: Specific piece of code that can be called upon by entering its name. Used for repetition.
e.g. This would say hello (run the procedure) three times

code:

procedure hello put "Hello!!" end hello hello hello hello

Process: Specific piece of code that is supposed to run while other parts of the program are running. I do not recommend using them because this is not really the case, and processes in turing are squirrelly.

Now you know. Next time maybe you should ask on a help forum/topic.

Oh well he was in a topic talking about it why not ask?

You could aslo have looked in Turing Help