I think Nuke has that path hard-coded somewhere internally (which I also
found a little janky). I just ended up overriding nuke.defaultFontPathname
with a function that points at a central font directory instead.
-Nathan
-----Original Message-----
From: Howard Jones
Sent: Friday, January 31, 2014 3:13 AM
To: Nuke user discussion ; Nuke Python discussion
Subject: [Nuke-python] Default font pathname
Hi
I've been happily using [python nuke.defaultFontPathname()] in a slate node
on Windows and Mac for a number of years.
Just added some CentOS machines and I get this error
Cant read /use/share/fonts/truetype/Vera.ttf
which is fair enough as it's not there. However I haven't been able to see
how to get Nuke to use a font that is there. I've set up different fonts
through preferences but haven't found what is forcing the font. Nuke is fine
so it doesn't seem to be using it.
Is this broken in Nuke 8.0 or is this set somewhere that an RTFM could have
found? I can fix this through python but was hoping to not have to.
Thanks
H
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
