[Sidefx-houdini-list] shelves - prevent writing into custom version
ken.ouellette at gmail.com
Thu Jan 8 09:42:06 EST 2009
I've done both in the past... .nosave and read-only.. all good things.
There was talk at one point about proper hierarchical preferences being part
of the 9 releases, I'm not sure where that ended up.
If you find a preference where the .nosave doesn't work (there were a few
if memory serves me correctly). I'd put it in as a bug ;)
On Thu, Jan 8, 2009 at 1:17 AM, Peter Bowmar <pbowmar at gmail.com> wrote:
> Good question, this is a real problem in Maya too apparently.
> For a lot of config files you can add .nosave suffix that prevents
> artists from modifying the config file, hopefully that works with
> For any *nix production pipeline making it read-only is a viable
> option though, I'd think.
> Peter B
> 2009/1/6 Robert D.M. Smith <robert.dm.smith at gmail.com>:
> > Here's one for ya ...
> > Let's say I've created a custom shelf set to be used throughout a studio.
> > The file is located in a specific location on the network.
> > During a Houdini session, an artist adds this custom shelf set & they add
> > new shelf to this shelf set. They save the shelf to their home Houdini
> > directory. Unfortunately, this process has added a memberToolshelf entry
> > the custom shelf - polluting the file.
> > Aside from making the custom shelf file read-only, are there any other
> > tools/commands to prevent writing to the custom shelf? Is there a way to
> > hide the 'New Shelf' choice in the menu?
> > Cheers,
> > Rob
> > _______________________________________________
> > Sidefx-houdini-list mailing list
> > Sidefx-houdini-list at sidefx.com
> > https://lists.sidefx.com:443/mailman/listinfo/sidefx-houdini-list
> Sidefx-houdini-list mailing list
> Sidefx-houdini-list at sidefx.com
More information about the Sidefx-houdini-list