Part Library Folders

Folder Organisation

The part library is made of GIF format images and XML files all stored inside the subfolder named "parts" of the BlueBrick installation folder.

 

            ← This is the part library folder.

This folder is parsed when the application is launched and is needed for BlueBrick to run. You can create as many subfolders as you want in the "parts" folder, but only one depth level is supported. Parts placed in folders within a subfolder will be ignored. Parts which are placed directly in the "parts" folder will also be ignored.

The original organisation of the "parts" folder is:
parts
  ├─ Baseplate
  ├─ Custom
  ├─ Duplo
  ├─ Logo
  ├─ Rail
  ├─ Road
  └─ Set

And here is an example of modification of the parts folder:
parts    ← If you add parts in this folder they will be ignored
  ├─ Baseplate
  │  └─ My Baseplate    ← This folder will be ignored
  ├─ Custom
  ├─ Duplo
  ├─ Logo
  ├─ My Parts    ← This folder is ok
  ├─ Rail
  ├─ Road
  └─ Set

BlueBrick folder parsing

For each subfolder of the "parts" folder, BlueBrick will create a Tab page in the parts panel. The name of the Tab page is the same as the folder. You can choose any folder name and include space and accentuated characters. You can also rename, delete or reorganize the original folders as you like as they are not used to identify the parts. The folders are just a convenient container to group the parts together in different Tab Pages in the Brick library. The downside is that every part name in the whole library must be unique, and the part name is the id that is saved in the map file. Usually this is not a big problem since every Lego© part already has a unique number.

When creating the parts library, BlueBrick first looks for GIF files in the parts folders. For each GIF file that is found, BlueBrick then checks if an XML file of the same name exists. XML files are optional and if the XML file is missing, default values will be used for this part.

Then BlueBrick looks for XML file without an associated GIF file and will also parse these XML files. These parts can be of two types: either it is a group part, or a normal part. If it is a group part, the image of the group will be recreated by BlueBrick (that's why they don't have gif associated) and visible in the part window pane. If it is a normal part, then this part will be ignored by BlueBrick, which means that they will not be visible in the part window pane. Those parts will also not be visible on a layout and won't generate a warning if BlueBrick finds them in a layout file. So if you want to force BlueBrick to ignore some specific parts, you just need to create the correct XML file.

GIF presentGIF missing
XML present
Valid Part
The part is visible in the library.
The behavior of the part is correct.
Group Part
The image is created by BlueBrick.
The behavior of the part is correct.
or Ignored Part
The part is not visible in BlueBrick.
Some information can be used for export.
XML missing
Simple Image
The part is visible in the library.
The part is inert.
Missing Part
The part will appear as a red cross.
The part is inert.