Load a layer set after Virtuoso opens

I don't think there's a way currently. How did this file magically appear in the layerSet directory? If it was via automation, wouldn't it be better to add it into the directory using pteImportLayerSet?

Andrew.

"Better" in the sense that there are no alternatives, I guess.  Many users won't have write permissions to more global repositories, so pteImportLayerSet() won't work for them unless they import it to their directories, and now you have layer set files for each of your users that you have to maintain.

And yes, these files are generated using an external tool, since editing layer sets using the layer palette is far more pain than we want to put our users through.

Given that Virtuoso has the logic to check the layer set repositories already, I'd think it would be better if there were a function that just reloaded them all instead of having to write Skill to find those same files and load them in.

It's very frustrating that Virtuoso can't read in a layer set without being obligated to manipulate the file system.

pteImportLayerSet can import to other locations - not just the user working area .cadence directory. Presumably the external tool has write access to the central area, so I assumed that this external tool could generate the files in a temporary location (say under /tmp) and then SKILL could import them into the central area. Of course, I may have misunderstood your setup.

Anyway, the long and short of it is that I don't think we anticipated your slightly unusual use model - and hence the gap in the (fairly comprehensive) "pte" SKILL API. It's a reasonable enhancement request though, so I suggest you contact customer support and ask for such an enhancement.

Regards,

Andrew

One of my scenarios is that I add a layer set to a project-level repository, which users don't have write access to.  I want users to be able to get this layer set, but not have to restart Virtuoso whenever that happens.  In that case, the user's Virtuoso session can't import it unless it gets imported to their home directory, which kind of defeats the purpose of putting it at the project level.

I appreciate your help.  My frustration with the pte API is that, while you can do (almost) anything you want, it is extremely context-limited.

One of my scenarios is that I add a layer set to a project-level repository, which users don't have write access to.  I want users to be able to get this layer set, but not have to restart Virtuoso whenever that happens.  In that case, the user's Virtuoso session can't import it unless it gets imported to their home directory, which kind of defeats the purpose of putting it at the project level.

I appreciate your help.  My frustration with the pte API is that, while you can do (almost) anything you want, it is extremely context-limited.