SM 07.76 - Structural_Shapes

This has been mentioned before, but the above config only allows us to set one xml file for use. It would be nice if we could use the function on Structural_Shapes to set multiple section files and then lock their selection so users can't pick other files.

Parents Reply Children
  • This isn't a new request Denis and would be a BIG help.

    Thanks,



  • You can already define multple sections by using an append within the configuration file:

    STRUCTURAL_SHAPES = us.xml

    STRUCTURAL_SHAPES > uk.xml

    STRUCTURAL_SHAPES > bear.xml

    Or in the Workspace Config dialog by using a semi-colon between the section file names; e.g., us.xml; uk.xml; bear.xml, etc.

    I'm not really sure why the variable doesn't like to be locked though...



  • Not only does it not like being locked Steve, but users can add and remove any xml file even if it's set in the config. Almost as though the config is not associated with the tool. I've got one user with 5 xml files attached, I can't even get the config to load just those listed. Really, the dialog needs to be more associated with the variable. Also, hadn't notice this before, but the config STRUCTURAL_SHAPES doesn't 'add' files like other configs, MS_RFDIR, do. You can't build a set of files from the Workspace\Config dialog as each entry  overrides the last one. You can only build up a list on the cfg files. I should have double checked this as I do this in XM.



  • The variable isn't intended to define the *only* sections to be loaded, just the default sections to be loaded.  The user is always able to add section files as needed.  And I believe once that is done, the additional files loaded are written to the stfprefs.rsc file.  So as long as the file is intact, the default sections defined by STRUCTURAL_SHAPES and the additional files included in stfprefs.rsc will all be loaded.

    In regards to building a list in the workspace dialog, this works as long as you include a semicolon between the section file names.  I know it's not exactly the same, but it does work...     :)



  • What I'm looking for Steve, and have been for some time, is the ability to set a std list of section files and lock it. I don't want users picking their own section files and don't see a need for them to. To me, this should be a config defined operation that can be locked down.