I bet my boots (and trousers into the bargain) you are as shrewd at Fbsl as I am or even smarter!
In fact so smart that I'm on the verge of assuming it was you who authored that bloody Fbsl Virus Writing Guide that's been hanging on the net for years now...
Well, if you find Fbsl too hair-shirt in the way of controls, you can always turn the corner to Delphi to get yourself buried under such a heap of pre-built TTypes that you can hardly find a place on your desktop for you to code at...
Quote SideshowBob: "How much do we want the data refined for us?"
<=== "Listen to the wise man!" -- one more quote, this time from another perennial and unfathomable source of inspiration, Queen - The Prophet's Song Lyrics
. IMHO what we're trying to do is encourage people to code rather than play children's toy blocks sitting in a sandbox.
Still, I can understand very well your indignation taking into account those hundreds of texture files you have to load into Xandreale together with each of your beautiful models. By the way, is Xandreale using that wonderful GUI you had in your MilkFarm MS3D Explorer -= Beta =-, may I ask?
Now seriously, what you are looking for is SysTreeView32 which you can find in your FMFD Controls panel under the name "Tree View". The examples of how it in fact looks when populated with meaningful content can be found on the left-hand panel of your own MS3D Explorer or, alternatively, on the right-hand panel of my dummy FSF GUI whose source code should still be there somewhere on one of your numerous hard disks.
The both versions are fully operational and responsive to mouse clicks. Keyboard control can easily be added too. In all other respects they are an exact replica of standard VB6 IDE Project Explorer tree view window.
To use them the file explorer style, you should populate them adding appropriate icons and file name entries in a recursive FindFirst/FindNext loop. Icon extraction for standard file associations may be too laborious and will certainly distract the user's attention from the main window of your application. So I'd recommend using a minimum of 3 pre-loaded icons only: one for folder/subfolder nodes, another one for all image files, and the third one, for all non-image files. If you are patient enough, you can use the entire set of image file icons precompiled into your MS3D Explorer (use ResHacker or PEExplorer to get them back if you don't have them any more) and design your own icons for model files (ms3d is already there in MS3D Explorer too).
By the way, the old orthogonal view icons (greenish boxes) you used in your MS3D Explorer distro were plain ugly. I had a set of more attractive icons ready that followed the general look-and-feel much better but you never asked.
Cheers and please take it easy -- in fact, my real self is soft and fluffy and purring like a kitten in a Whiskas TV commercial!
Hoping this helps,