Feature Request: String expansion should resolve in filebrowsers.

[melMass]

I'm building a simple Send shot to Gaffer script that autogenerates gfr projects from Nuke, Maya or Houdini.

Among other things it creates script variables ${scene:platesDir}, ${scene:nkScript}etc etc..

I'm mainly using them using string expansion. All works perfectly but I think the file browser should be aware of string expansions as well. For now the only way to check that the path did resolve is to check downstream outputs.

[andrewkaufman]

When you say the file browser, do you mean the application File->Open menu? Or the cache/image browsers associated with a given SceneReader or ImageReader node?

[melMass]

@andrewkaufman Sorry for the delay. I haven't look at the sources yet but I think I'm only referring to tweaking the FileSystemPathPlugValueWidget

A simple example: I want to store the path to my lookdev hdri's in a script variable. I then have a command that creates an Ai Image with ${scene:LD} (my script var), as a default path. I'm expecting the browser to expand, either truly (fullpath) or Houdini like ($HIP/), but bring me to the folder content anyway.

I hope this is clearer to understand.

Thanks

[melMass]

And also autocomplete from the lineEdit like here: http://www.gafferhq.org/blog/path-widget-autocomplete/

[andrewkaufman]

ok, thanks for clarifying