Hey guys,

From what i could see theres no way to set where the jump.pref lives?
Im wanting to create some project specfic jump.prefs.

At the momment this is saved into the houdini program folder. I would have assumed that this would be a user setting, but it doesnt get saved into the user folder.

Is there anyway to set where the jump.pref lives, it would be great if we could define a main set of jumps in our application config, and have a prject specfic version then also have user defined jumps.

Also even tho I have removed the jump.pref from the application folder, the jump locations still exist after restarting houdini. Is there somewhere else that these locations are stored?

Thanks
Nick

Ok i had another jump.pref file somewhere in my config. after some experimention it looks to be that I can have jump.pref files in the three places i want them to be in but when ever any favourites are added to the jump file it looks to be that all paths are compiled and written across all jump.pref files.

I think it would be great if the jump.pref file could handled with some environment variables directly.

For now i can probably deal with these by locking the files apart from the user based one.

poking around to try and do this myself...

I make use of environment variables in linux, which allows me to jump to a few locations quickly in the filebrowser,
but I want to be able to make these locations persistent across different versions of Houdini at a studio level,
as opposed to it being managed in a users `~/houdiniXX.X` - which is a nice user managed overlay.

For example, `${REF_ROOT}/scenes/houdini/${HOUDINI_MAJOR_RELEASE}.${HOUDINI_MINOR_RELEASE}`

I just tried putting this elsewhere in the ${HOUDINI_PATH}, launched 19.5/20.0/20.5 and it works fine!
Whatever is in the `jump.pref` gets pushed into the "Look In" field at the top of the filebrowser,
so if its respected there it will work without the variables needing to be resolved.
The variables are expanded when saving down to the user `jump.pref` which is perfect.

One thing tho, it appears that if this `jump.pref` is found in the HOUDINI_PATH at the studio level, and a user tries to bookmark another file location it will be written to the studio `jump.pref`.

I gave the file read only permissions and tried to do the same. It resolved the environment variable from the "Look In" field to the filebrowser bookmark location while the filebrowser was open and did not write to the locked studio `jump.pref` or the user `jump.pref`. The new bookmark disappears when the filebrowser is next opened.

This is fine from a studio perspective, but suggests if `jump.pref` was picked up higher in the `HOUDINI_PATH` that would be the one Houdini would read/write to, such as `$HOUDINI_USER_PREF_DIR`

I also tried to add a few additional paths to `$HOUDINI_USER_PREF_DIR/jump.pref`.
Additional `jump.pref` files in the HOUDINI_PATH are respected.
Creating a new filebrowser bookmark at this point will persist for the houdini session,
but wont be written down to either `jump.pref`, likely because the studio level one is higher in the path and read only.