because we are using static ResourceLocatorTool, multi-threaded resource loading may conflict each other.
Between Static and instancing version of ResourceLocatorTool, what is better?
Same goes for TextureManager- can't use it from multiple threads.
ResourceLocatorTool finds resources by reverse order of ResourceLocator.addResourceLocator()
It is confusing to me. I'm curious about what is generally rational.
Probably no rational, it is just using recursion and is just taking the last 'thing' off the list. So it's working like a stack, to work like a queue one would simple pull from the starting index rather than the last...
To fix the locator tool? Its not broken and unless there is a good reason for changing the order, I see no reason to rock the boat (but that's just me…). Perhaps others have a differing opinion.
Regarding order, I'd say I prefer it the way it is.
My use case: you have several directories with application data, then you add some other directories for user mods. You would wish the latter to override the former.