my guess it is a workplace shell limitation at this time. Rich had said WPShell was a mess
No, I said Dynamic Icons was a mess. Multiple shortcomings prevent Details view support and limit Tree view to the same sized icons as Icon view. Here's why:
1) DI's "dirty little secret" is that it creates a separate, standalone PNG image for every single object you see during a session. When you open a folder with 100 JPGs, it generates 100 png images each requiring 16k. The same is true for every folder, every datafile, every everything. Over the course of a session you could end up with thousands of images.
2) DI caches these images to avoid the compute-intensive job of recreating them. However, each object can only cache one icon. If you display an object in Icon view at 64 pixels, then open the same folder in Details view using 32 pixel icons, DI will have to destroy all of the 64px images and recreate them at 32px. In a worst-case scenario where both views are open, DI might have to destroy and recreate every icon for every refresh!
Happily, there's a solution in the pipeline for #1. After our earlier discussion, I rewrote large parts of DI to eliminate duplicate icons as much as possible. Some users may see an 80-90% reduction in DI's memory usage when AN releases it. However, it will require a thoroughly revised 'bigicons.txt' file to achieve these savings.
@David, could you send me a PM with your email address so we can discuss this and exchange files?
Sadly, the shortcomings that prevent Details view support and limit Tree view will remain for the foreseeable future...