That's the thing.  If the geometry or texture file is in the Geometries or Textures folder, the reference is correct, and the folder name hasn't changed - then Poser should find that exact file every time.  Otherwise, stop renaming the darned subfolders there or the reference path is incorrect - both stupidity (user or merchant).

But it is my understanding that Poser always takes the first match encounter no matter the fact that the actual file resides where it should - which is poor, poor coding if that is the case.  In other words, I don't care if you have 10,000,000 'gold.jpg' files in your runtime - if the relative path to each is unique then it should ALWAYS resolve to the correct one.  If this isn't how Poser works, maybe we should pressure the developers to work for their income...

This would need to be verified, but it sounds that if the file path is correct Poser will still take the first filename match.  Otherwise, there would never be contention as long as users don't meddle in the Geometries/Textures folders and the merchants use proper relative paths: ":Runtime:Textures:Hithere:HereItIs:Gold.jpg" should work every time to reference that particular file as long as it is a valid path.

This is why I challenge the veracity of Poser rather than merchants.  I have yet to encounter a merchant texture reference like: textureMap "gold.jpg".  This may happen on occasion, but the overall feeling reading this thread seems to be that even - textureMap ":Runtime:Hithere:HereItIs:gold.jpg" - incurs the same situation.  Otherwise the point would be moot.

Note that I'm not arguing one way or another here - just trying to discover why "gold.jpg" as a file name has such visceral reactions when, in the proper folder hierarchical context, it shouldn't even be noticed.

ETA: I understand that Poser will do a search and take the first opportunistic filename match when it cannot find it otherwise.  But that is just the practice.  I do the same (see other post).  It doesn't mean that it will find the correct match just that the search will try to resolve a missing reference.  I did the same because it is better to seek and to find than to pester the user first. :)  This is not a user, merchant, Poser matter specifically.  If the product is proper and the user puts things as they should be then Poser should find the referenced file.  I can sympathize with those who have found products that are incorrect (bad reference paths, missing files).  These things should be rooted out by testers (ehhem).  In other words, such occurences aren't one single responsibility (though most of it lies on the merchant's shoulders).  Poser does 'the best that it can to resolve a reference when all other avenues fail.  Maybe a better approach would be that when Poser finds a match through search, to ask the user to use that or select another (?).

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone