@theoryshaw yeah - I'd consider it a bug. Thanks for reporting and the video makes it super clear :) Will fix!

@theoryshaw fantastic idea! Will do so - in the future can you add these to the github issue tracker? Good to be all in one place :) I almost didn't notice these comments (peertube didn't send email notifications)

@theoryshaw for the time being, I'll prefer to leave it separate, with the following reasons:

1. If a user does want that behaviour, it's two extra clicks away (right click collection -> select objects), so it isn't prohibitively difficult
2. Making it the default behaviour in Blender requires creating extra "parenting" relationships. This works for a small project < 10,000 objects, but starts turning into a hindrance for large projects. Especially if you accidentally move the level :)
3. One design consideration in BlenderBIM is to focus on BIM data, and not impose rules on how geometry is constructed, including whether or not this relationship exists. This allows other developers to build as they see fit, or the modeler to model as they see fit. For example, in Archipack, your desired behaviour is the default, and it integrates very easily with Blender. Similarly, I've modeled a bit more freeform and less parametrically where I've enjoyed the ability to parent anything to anything, which also integrates easily. Kinda like the AC/DC current issue - easy to integrate restrictive into a lax default, hard to do the other way around.

@theoryshaw Ah yes I should probably mention - on occasion (not too often, thankfully!), it is not sufficient to just replace those files. The most common scenario when this happens is when I upgrade to a newer build of a dependency (most commonly IfcOpenShell) which includes features that the previous version did not - since dependencies are not in the repo. To guard against this, either you can watch the changes in the Makefile (https://github.com/IfcOpenShell/IfcOpenShell/commits/v0.6.0/src/ifcblenderexport/Makefile ) or you can just wait for the official release and be sure to have a clean install for each official release (since the official build I release includes all dependency upgrades).

When that type of change occurs, if there has been an official release (like 2 days ago) then that's an easy way to upgrade. If not, it requires manually replacing the dependency (again, most commonly IfcOpenShell here: https://github.com/IfcOpenShell/IfcOpenShell/blob/ebc305c0e1de3cab99e05da34a134bf4c89ebe30/src/ifcblenderexport/Makefile#L28 ) in the `addons/blenderbim/libs/site/packages/*` folder.

So for example on June 11 I edited the Makefile to get a brand new IfcOpenShell feature which allows black/whitelisting element on import - since you only updated the BlenderBIM Add-on code but not IfcOpenShell, that's why you run into that error. The easiest fix is to start clean and install the official release from 2 days ago, then you can continue to do the file replacement method exactly as you've shown in your video :)

Hope it made sense.