Hey J -
I don't know if this is what Nuke uses, but it seems to work for us where there
is potential for illegal chars:
import re
CHARFIX = re.compile("""[^\w]""")
layerName = CHARFIX.sub('_', layerName)
Cleans up the stuff that shouldn't be there for knobs and names. I've been able
to create illegal names (like your roto exporter?), but then the names and
knobs break or change to something legal when the script is reloaded. It would
be nice if it wasn't allowed in the first place.
JRAB
On Jan 28, 2012, at 2:51 AM, J Bills wrote:
> howdy! thought someone here might have the answer to this
>
> I'm trying to find out exactly what sort of node name filtering heuristic
> that nuke runs oncreate
>
> We have a roto exporter that is somehow able to script illegal names in nuke
> and all appears well at first but once you start trying to parent expressions
> or whatnot, things quickly break. so I want to make sure our naming from the
> roto app is getting the same filtering as it comes across the Nuke.
>
> I couldn't find anything in the dev guide - anyone come across the info
> before?
>
> thanks!
> _______________________________________________
> Nuke-python mailing list
> [email protected], http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
