Hello friends.

with the purpose of maintaining the proper functioning of my functions that are linked to a DLL, i need use the function "wait_for" always after performing some function of the dll.
Sample:


This Became too boring, because I need to do this many, many times throughout the script. (wait_for()...wait_for() ...)

Is there any way to create a macro linked to functions?
Whenever I call a function, it automatically performs another function in end?

Change the typedef if you need params

Chaos, I'm pretty sure Neo wanted to automate the wait_for(), not have a callback function...

Which, by the way, doesn't work. Nor does it need to, because wait_for() will always return immediately, since Neos DLL method will never ever be registered as still running in the engines Scheduler (no will it ever appear there as anything). No idea why he thought wait_for() is needed there, but it's definitely not.

Hm probably I understood it wrong.
However, he should code his own wait_for function, like a while which waits until iSelection is bigger then -1 or something.

But why?! iSelection (by the way, you are doing hungarian notation wrong) doesn't change after sql_select was called. Ever.

Well then I completely missunderstood what he wants to achieve sry.

The code from the original poster is already flawed. That's the problem. He has misunderstood the conception of wait and return.

Exactly (^.^).



I really did not know that. Thanks for clarifying.
however, the lack of it generates crash in my functions, since sometimes the function attempts to validate variables that have not time to get a true value.

below show an excerpt from my script that fails to validate a true value if I do not use a standby.




If I remove the wait_for of the script, the "if(results)" may not receive a true value, because the function of the DLL may not havê had time to return a valid result.

believe then that the most efficient way would be to use a simple "wait(1);". This is correct?

You should read my post again, I said something like that before.
Just change the dll function or do it like this:


true == 1
false == 0

-1 should stay as long as the function didnt return ANYTHING.

You both misunderstand the concept of "return". You cannot mix wait and return.

The first possibility is that sql_get_rows immediately returns a value. In this case iResults has a meaningful value and waiting may either happen forever (because sql_get_rows returned -1) or may not happen at all (because sql_get_rows returned something different).

The second possibility is that sql_get_rows does not return anything. In this case iResults is either random or remains at -1. I don't know. try it if you're interested.

Regardless of the possibilities described above iResults will never change afterwards so that the while loop is pointless.