OBD U6 - Catalog Editor vs Config Dialog

Working through changes to the build and I'm getting an exception error when loading the build which I think is related to the old catalogs. Only issue is that i can't get the correct paths to load.

in the config dialog, both:

DG_PATH  

and

DG_CATALOGS_PATH

show correctly:

When I open the Catalog Editor you have it point to another local directory. Has anyone else come across this before?

I have them locked now as it appeared they were being changed down the line (not sure where at the moment). Anyone else come across this?

All help appreciated.

Parents
  • Hi Sean,

    DG_CATALOGS_PATH is a child variable driven by preceding variables such as TFDIR, it should not be locked.

    Out of the box TFDIR points to the installed datasets and includes folders at Organization, WorkSpace ad WorkSet levels.

    TFDIR is defined by $(TF_DATASETS)$(TF_DATASETNAME)\

    I'm assuming that a) you want the default dataset to be in the N:\ path shown above, where you copy Dataset AU to the network and customise it to your needs, and b) your dataset update strategy is to pull in updates from future dataset versions as they become available (e.g. additional or new content required for new/updated features)?

    Once you have defined the path to your network configuration using ConfigurationSetup.cfg, the standards CFGs in that location can modify TF_DATASETS to the appropriate path in your custom dataset.

    TF_DATASETNAME sits in the WorkSet.cfg, e.g. at line 14 TF_DATASETNAME = Dataset_AU.

    Hope this helps to set you in the right direction?

    Marc

  • 'Hope this helps to set you in the right direction?'

    Not really, the problem I now have is because it seems we're forced down a config path is breaks what I need to happen. I'm not interested in returning to a situation where ucf files create chaos. 

    I need to work with this more.



  • Hi Bear,

    Sorry for the late reply.

    I've been on holiday for the last two weeks.

    Tuan is correct, the -ws prefix was causing all my problems.

    He solved it by suggesting I use the SET command prior to starting OBD.

    I run my builds from a batch file using the following code:

    @echo off
    set _USTN_CUSTOM_CONFIGURATION=M:\CAD_Build_OBD_BHP\Configuration\
    START "" "C:\Program Files\Bentley\OpenBuildings CONNECT Edition\OpenBuildingsDesigner\OpenBuildingsDesigner.exe"

  • Bummer, looks like I'm going to need to try another work around. I use a cfg file in the appl directory, this is why I hate these sorts of changes.



  • These fixed name cfg files are unnecessary, JMO.

    So, I've changed the name of the cfg file I use in the appl directory to ConfigurationSetup.cfg.

    I have then changed my other build cfg to WorkSpaceSetup.cfg

    All of the variables are still being set, but the path displayed in the catalog editor still refers back to the default location even though the path doesn't appear anywhere in the config dialog.



  • I would refrain from renaming default files as there's always the possibility that a file name is hardcoded somewhere. 

  • I'm not renaming default files, would never do that, but the cfg file I use in the appl directory usually has a name I give it. It still seems to do everything it did before since I used Marc's suggestion with:

    %undef _TF_WORKSPACEROOT

    My last hurdle is the Catalog Editor, which hasn't been an issue in the past and these hardcoded cfg names do concern me. 



Reply Children
No Data