[quote:3e7lt2rs]- Pathfinding could fire "then" after the path is found
Doesn't it already work like that, "On path found"? What would be different or the benefit?
[quote:3e7lt2rs]Does anyone have any thoughts about this? Good idea or bad idea? Perhaps there's an even better way it could be approached?
Im not 100% sure I understand the benefit in this. Completely agree with the "When data loaded" kind of thing, which is very useful.
But if you make a game and do a Async read of data, wont the data be to old when needed as you write the game will continue on. So when the data is actually need you would have to get it once more, in case it have changed.
Wouldn't that leave two options, either you have to make sure that the data is there when you need it, so would require you to wait for it regardless of how it is read?
The other one is that if you have a program that requires to load larger amount of data, you would wait for it to load. So you would put it at the start of layout or somewhere where you would wait for it to load, or it would be data that will not "impact" the game, so it wouldn't really matter if it was read as Async or not.
But maybe I just misunderstood the benefits?
As I see it the problem with Wait is that it just wait a specific time, which is fine for what it should be used for. But often it is used to "Trick" the code. Which is not nice I think. Whereas "Wait for signal" will allow the program to wait for something to be done or happen before moving on.
So maybe a better idea is to just add more "Finalize triggers" to different things. Like you have "On path found" etc. It could be "On local data read", "On local data written", "On audio file loaded", "On video loaded" and so forth.
Or is that not what you are trying to achieve with this?
But regardless I do agree that "Then" is probably a bit confusing name. Then "Async. completed" or something might be better.