No it's apparently not coming until next year, and will cost $'s (P6). Whether it'll fix bugs - as the current (and the previous) CEO promised - or add features and bugs - as the survey effort seems to indicate - we won't know until ... some time after P6 ships.

I agree that they needed to speed up .png thumbnail display - it's even a problem on PP - but could they really not have speeded up the actually .png display code itself - on 4 year old code? I too find "Oh our .png display code is too slow for you, then let us turn it off for you" a tad insulting. (Even switching it back to .rsr would have speeded it up.)

And to rub it in they choose a relatively low value, and instruct you to use an editor to raise it! If they weren't at least going to address it via a Prefs setting in the ui, they could at least have set the default to something innocuous like 1000. I predict we'll see a steady stream of "What happened to my thumbnails?" posts in the future months. Like we do for shrinking library names, and the scene window off the upper left of window, and ...

What were they thinking? I'd REALLY like to see CL's definition of when a product is "good enough" to stop fixing it. It might make interesting reading. (I'm guessing it's along the "when it gets too hard" lines, rather than anything objective ;-)

And to avoid someone else having to say it, yes I am still "ungrateful" for CL shipping but not fixing all of it's problems in 18 months (on a release that appears to have had less than that as a development schedule). And yes, I'd still take my money back in exchange for putting my copy of the software out of its misery if they'd give it to me.