These solutions aren't really great solutions to this problem at all.. just sloppy workarounds that users have to do in order to get this sh/t working the way they want it..but its far from perfect... I don't want ALL my explorer windows to opening up at the same size EVERYTIME... you can get addons to do that.. unfortunately none of them have ability to look at previous saved explorer window sizes and see if they have been adjusted.. then leave them.. and most are sloppy in that you'll still see the window opening at Explorers set size and then adjusted to your custom size/... its just *. Obviously if a specific folder like a folder where i've wanted more colunm details showing etc... and the window dimensions were adjusted then most likely thats how I'd be wanting to see that folder the next time, not that the new custom size.
To me it would just make sense if they original settings that dicates what newly created explorer window sizes was opened up and made customizable... along with some more user friendly explorer customizability( like movie thumbnail generation settings! maybe even the ability to set the frame capture % within the file myself... maybe even mouseover animated thumbnail display within explorer, like from 4~ captured frames of a movie file)
But this Windows Explorer <a bag sh/t, with extra smelly toppings if its Vista Exploder, but hey its just like such a key area of Windows OS (hope C9 doesn't EVER interview that team)... and turns out the reason Adobe still haven't bothered getting a proper STABLE thumbnail support working for any of there applications in explorer.. is..... surprise, surprise... because of the whatever Explorer API's .... well no bloody surprise there.. they've only just dropped official explrer thumbnail support for xnumber of years since PS7.. when they ditched the support because of countless user complaints about the bugs. That problem still exists in Vista... no wonder they force installation of that Bridge sh/t on CS suite installations. Thanks MS, I love bridge NOT
Chris Cox - 1:44pm Dec 2, 08 PST
Adobe Photoshop Engineer
As I already said: the Microsoft API is broken. For one thing it leaves files open and fails to close them, so you get complaints about "the file is open or in use" when you shouldn't. Adobe cannot always work around something that is broken at the OS/Explorer level.