I’ve been using this component for a while. Todays update showed some errors which seem to be related to the custom preview component.
What is the transform input for?
Hi @martinsiegrist I didn’t make that change so I would need to check with Kike about it and he’s currently away from the office, but that looks like it’s a hidden component, right? I’m guessing that’s a temporary prototype that Kike has been working on and wasn’t necessarily meant for public use (hence why it’s hidden). I’ll have to try to ask him when he returns.
I’ve made a complaint about this component stopped working today. It is one of the best things in V9, working with no problems. Why would you erase it?
@AndyPayne feel free to merge the two topics if you want…
As I mentioned, I didn’t make the change so I don’t exactly know what or why the Transform input was added. I believe this component was a prototype for a re-write of the Custom Preview component, but it wasn’t completely working in all cases which is why it was still in the hidden state.
I just reverted to the BETA from last week after the new version didn’t load my file.
This issue should be fixed in the next BETA release. Basically, the issue was that when Kike added the new Transform input parameter, he placed it at the beginning of the list of parameters which was throwing everything off when it got deserialized. I’ve moved the Transform input parameter to the end of the parameter list and now everything should get deserialized correctly. I’ll let Kike review things further when he returns.
Ok thanks, so I guess I’ll just wait for the next Beta release?
I could send you a dujour build (likely tomorrow morning) which would contain the fix if you need it ASAP.
I can wait until Wednesday.
I’m OK too, though I already replaced it in like a 30 places in my script 
Thanks for updating this. From my experience it has better performance than standard combo: preview + extracted edges (no flickering) and is easier to configure (everything at hand). Very useful component.