[Request] TimerDelta

If you've read this thread you know that Clickteam implemented Timer based movement. It would be very nice if we could take advantage of this with our own custom movements.
To do this we need to calculate the time passed since the previous loop. Of course Clickteam already does this, and François just told me the relevant bit. The value to get is:

Code:

---

rhPtr->rhTimerDelta;

---

So my request is pretty simple. Could an extension developer be kind enough to write a very quick extension? It only needs to return the one expression above.
Clickteam will most probably implement this via a new system expression in a future build. So the use of the extension will be temporary.

rhPtr with an H? I have to be honest and say that I've never seen that variable! :I

It is probably a pointer to runtime Headerobject. I think you can access it by: rdPtr->rHo

http://hypothermia-game.com/rhTimerDelta.zip there you go.. havnt tested it

Aww you beat me to it :P

Thank you very very much Villy. I've made some tests and the extension seems to be working great. But I get approximately the same result than 1000.0 / FrameRate.
So I wonder if using one or the other (to factor speed) makes any difference?

Anyway I really appreciate your help Villy. :)

Doesn't the mathematical operator 'delta' mean difference? for example: 12.54 delta 8.76 = 3.78, so what doe's timerdelta do?

If you read the original post (which I highly doubt from your track record),

Quote:

---

To do this we need to calculate the time passed since the previous loop.

---

Therefore, it is the difference in time between the last loop and the current loop.

Quote:

---

Originally Posted by Werbad

It is probably a pointer to runtime Headerobject. I think you can access it by: rdPtr->rHo

---

Yep, true AFAIK. But rHo is not a pointer to the runtime header thought, so you access its member with the '.' operator.

not sure what you meant by that, but rdPtr is a pointer ot the rundata structure and thus it's members are accessed with '->'
the rHo is not a pointer and thus it's members is accessed with '.'

fprh rhPtr = rdPtr->rHo.hoAdRunHeader;

I still wonder which method is the most reliable, in the case where the speed of the application fluctuates very much. According to you, is it better to use the first or the second line of code below?

Code:

---

"Active" Set X position to X( "Active" ) + 100 * ( 1.0 / FrameRate )

"Active" Set X position to X( "Active" ) + 100 * ( rhTimerDelta / 1000.0 )

---