ThomasWilshaw
ThomasWilshaw
Might it be better to wrap the lines [here](https://github.com/PixarAnimationStudios/OpenTimelineIO/blob/3e4b4591409a4afce92ca7b2bc9cb94c7f756426/src/py-opentimelineio/opentimelineio-bindings/otio_serializableObjects.cpp#L702) rather than trying to do it automatically and risking wrapping very long commands that should probably stay on a single line?
How does that look? It's been a while since Ive written any Python code so there may be a nicer/better way to do it.
Done, but for some reason there has been a change in the text that's nothing to do with the Python code
I've just updated this. I had an older version of OTIO in my Python setup that was messing things up
No problem, sorry I've dropped off the radar for a while, I've been very busy of late. That's the CLA all done, please let me know if there are any...
There were a few other places but they were all single line commands rather than blocks of text and I assume should be left as a single line?
I think it would be great if the CIE role became a requirement for all configs to give a ground reference for doing colour work in apps that is outside...
I had always assumed there would be a text editor in the param view (similar ot the rich text node) but I suppose you could always have a file path...
I see what you mean yes, a single line would get very messy > I was thinking a separate dialog because shaders can get long quickly, and a more code-friendly...
I think that is correct yes. I'd add that edits within the text editor would also need to be undoable commands and put Olive in an unsaved state. I think...