Heh, that's a bit frustrating. Never noticed that one before. I tried creating "first" and "last" int knobs on a NoOp along with the File_Knob, thinking it might populate those "magic" knobs like on a Read, but it doesn't. The frame range seems lost when the panel closes. There seems to be no other way to access that frame range, no obvious method on the File_Knob. If I were you, I'd mail support with a feature request. In the meantime, your workaround is the way to go. -E
On Sat Jan 17 2015 at 9:18:40 AM Erwan Leroy <[email protected]> wrote: > Hi folks. > > I'm struggling with something that I thought was gonna be super easy. > > When I add a File_knob in a panel, click the little folder icon, it opens > the file browser just fine. I select a sequence, the field at the bottom > shows "/path/to/sequence/file_####.ext 0-100". > When I click open, what gets returned into the knob is > "/path/to/sequence/file_####.ext" > I'd like to be able to obtain the frame range as well, but I can't seem to > access the value. > > I found a work around by using a String_Knob coupled with a button running > fileSequence = nuke.getClipName('Select File Sequence'), which does return > the whole string. > Then I cut it up in pieces and use what I want, but just to be clean I'd > like to use the File_Knob, I'm sure there is a way, read nodes parse the > frame range from that all the time. > > Cheers > Erwan > _______________________________________________ > 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
