Why do we need a BB_Floormaster.dgnlib on Dataset-level when we refer to a file on another level (project)?

The Floor Manager is something you expect to be (and is) linked to a file which is on project-level, since you need to define project-specific things like site/building/floors.

Why is there in the dgnlib-folder a file called BB_FloorMaster.dgnlib in the Dataset too? This is a higher level then project, there is no use/need for it here.

Parents
  • Hi Stefan,

    This is there as a failsafe if a project for whatever reason does not contain a BB_FloorMaster.dgnlib.

    This location is defined in C:\Program Files (x86)\Bentley\AECOsimBuildingDesigner V8i Ss6\AECOsimBuildingDesigner\config\appl\BuildingDesigner.cfg as shown below using the ':' operator that directs 'use this unless defined elsewhere'.

    # Name of default Floor Master DGN seed file used by the floors tool.

    BB_FLOORMASTER_DGN : $(TFDIR)/dgnlib/BB_FloorMaster.dgnlib

    This operator is used in similar situations throughout ABD and all other MicroStation based configurations to define the base state for the applications before other levels of configuration are applied, generally to ensure that there is always a useable definition for a variable if subsequent levels, mostly site or project configuration do not address them.

    Regards

    Marc

    Answer Verified By: StefanC 

Reply
  • Hi Stefan,

    This is there as a failsafe if a project for whatever reason does not contain a BB_FloorMaster.dgnlib.

    This location is defined in C:\Program Files (x86)\Bentley\AECOsimBuildingDesigner V8i Ss6\AECOsimBuildingDesigner\config\appl\BuildingDesigner.cfg as shown below using the ':' operator that directs 'use this unless defined elsewhere'.

    # Name of default Floor Master DGN seed file used by the floors tool.

    BB_FLOORMASTER_DGN : $(TFDIR)/dgnlib/BB_FloorMaster.dgnlib

    This operator is used in similar situations throughout ABD and all other MicroStation based configurations to define the base state for the applications before other levels of configuration are applied, generally to ensure that there is always a useable definition for a variable if subsequent levels, mostly site or project configuration do not address them.

    Regards

    Marc

    Answer Verified By: StefanC 

Children