Here is what I have.
A dll/function that needs to read memory (ie players locations, etc.)
A exe that needs to display this info.
Only problem is that the function is CPU and HD intensive to execute. Therefore it shouldnt be stuck in a tight loop constantly updating.
Now, I've thought about injecting the dll and using a mutex/semphore to get reads done. And then have the exe/dll part wait on a mutex.
I've also thought about using a RemoteExecute version. Or even something like Hooking the window proc and catching SendMessage.
Any thoughts on the best practice/quickest way to handle this?
Ie from the time the exe wants the data, to reading data, to exe has data and can continue its work...
Also this is going to be called every few seconds.