(2016-12-04, 20:59)Roland Melkert Wrote: The spec doesn't mention it should also look in the parent's textures folder, LDView seems to do so though.
I don't think LDView will successfully load the texture if the part is used in a model, unless all the files go into a parts directory (either the official one or the unofficial one). LDView prepends textures/ onto the texture filename, and then uses its standard dat-finding path algorithm. One of the entries in LDView's search path is the main model's directory, so if you load this part into LDView, it should find the textures based on that. But if you use the part in an LDraw file located in a different directory, it shouldn't find the textures. (In that case, the LDraw file would need a path to find the .dat, which wouldn't be normal.)
If the part itself is put into either <LDraw>/Parts or <LDraw>/Unofficial/Parts, part-finding paths searches should work (and it looks like that would already work in LDCad). So I don't think there is anything wrong with your current search path, nor is there anything inherently wrong with Philo's part, since it's a fair assumption that all of its files will be placed in either an official or unofficial parts directory (or perhaps the directory containing the model it is part of).
The reason LDView looks in the main model's directory for files is because in the past before MPD became common, many LDraw models would make use of sub-models, but these sub-models would be separate files in the same directory as the main model. Technically LDCad should support this, but I'm not real sure it's all that important, since I doubt anybody uses that functionality these days.