Hi,

Im using engine_getscript to call a function.
But if that function hit's a wait in it, it will get terminated instead.
Why is this, and more importantly, can this be fixed (through a work-around or in the engine)?

regards,

also, sys_exit("whatever in here") quits the game without displaying any string whatsoever. (only when called through engine_getscript).

Hope this helps a bit more.

regards

What is your problem? sys_exit and wait are explained in the manual.

http://manual.3dgamestudio.net/aexit.htm

yes, but i am talking about a function that runs through engine_getscript.

If the function that runs through this contains a wait, it immediatly get terminated (without doing anything that's still in the function).
Same happens with sys_exit and a string parameter, no string is displayed, engine just shuts down.

That sounds perfectly normal to me. Have you read the manual? Can you describe your problem in detail?

ofcourse;
I'm running this piece of code from a model:



which is basically what the manual wrote (yes, i have defined "void runStringFunction();" global).

now, whatever function runs off of that works fine, untill the point it hits a wait in it. at that point, the whole function is terminated.
I wanted to know why that happens, and if there is a way around it?

regards,

For the third time: just read the manual. Of course it's terminated because wait always terminates a function.

"Wait temporarily terminates the function (like return), stores its local variables and the my and you pointers, stores the function state in an internal list (Scheduler List), and returns to the calling function (if any)."


A computer does not read your mind - it just does what you tell it to do.

yes, i got that part, it just doesnt return to the calling function after the wait, the whole function stops after it (and doesnt move on the next frame).

I just used the wrong terminology there, i'm sorry, "terminated" should've said "quit without resuming".

The manual doesnt say anything on that (not under engine_getscript or under wait).
Or i'm getting it completely wrong, and the manual should be more clear about that?

Hmm, what do you mean with "it doesn't return to the calling function"? The calling function does not continue?

the function that has the wait in it, doesnt continue running after the wait, when it was called through engine_getscript.
so yes, the calling function does not continue.