Components

Michael Mayer

I have an IFC import that brings in Windows and Doors as Components.
Each Window size uses its own Component.
Now I would like to edit the Component of a Window e.g. add/change Materials.

But I only can replace a Component or open a Copy (?)

Is there a way to just edit the Component in use in the file ?

Piet

Hi Michael,
did you try _bmExternalize? It makes the component external, then you can edit it and update with _BIMWINDOWUPDATE once the component is saved.

Michael Mayer

Piet said:

Hi Michael,
did you try _bmExternalize?

No,
so far I only used Tools that will appear in Quad, Toolboxes or Menus.
(Or maybe I have overseen it)

But that sounds like a solution that I have to try.

So it will extract the Component as a DWG (?)
I could extract all Windows, Doors, .... and put them into a sub folder
in my project file directory and edit them as I want (?)

I just wonder why the workaround, when the Components are already
in my file and only in my file. Why not just a REFEDIT, BLOCKEDIT ....
COMPONENTEDIT mode ?

(Isolated editing like BLOCKEDIT would be nice but editing in place
like REFEDIT would also be useful)

Michael Mayer

From the IFC import I also get a separate Component for each single
Window/Door, although I basically only have two "Styles" of Windows.
Which would be better and easier to control when having only a
"parent", with enough parametric control, Component.

I already was sceptic if I could edit and adapt my Windows and Doors
to changes that result from recent corrections to Wall geometry and
such things at all,
or if I would need to BRICSCADIFY and replace everything at the end
with Bricscad Components.
Now, thanks to you, I know that there are ways.

So I think a bit about what is easier at the end,
editing 30-40 external Components, replacing all with standard BC
Components or even build custom Windows and Doors (?)

(While the later may be a bit too much for me)

Piet

Hi Michael,
I think the reason refedit or Bedit can not be used is that components are parametric blocks and instances or 'anonymous blocks'.

Would it make sense to you to always work with external components? That a Bimproject always has a 'windows' subfolder.

Michael Mayer

Piet said:

Hi Michael,
Would it make sense to you to always work with external components? That a Bimproject always has a 'windows' subfolder.

I am not sure if I really understand the question

My top level inside my example project folders looks similar like this :
- App 1
- App 2
- App Bricscad
- ....
- Image Textures (used by all Apps !)
- Submittals (like site Photos, PDFs, Files in wrong - to be converted/imported - Formats....)


My parent Bricscad Folder should of course like this :
- Backups (previous project or version DWGs with a added datum Prefix)
- References/External (updated by clients)
Project Part 1.DWG
Project part 2. DWG
...
Project TIN.DWG
.....

In short, like with my other Apps, in my Project/Bricscad folder's 1st Level,
I never ever want to see any polluting things like :
*.BAK, *.DWL, *.DWL2, SQL Database, *.DS$, *.DST, generated Drawings, Project Settings, ...

I want to have control to sort everything from Bricscad Project Settings
in Sub Folders, before it gets too crowded and illegible.

And if there would come a "Windows" Sub Folder, of course not at first level,
but it should be more like :
- Libraries/Doors
- Libraries/Windows
- ......
same as it should be sorted in configurable Folders for all Drawings !
- Sections
- Plans
- Details
- ....

-----------------------------------------------------------------------

Piet said:

refedit or Bedit can not be used is that components are parametric blocks and instances or 'anonymous blocks'.

I never understood the concept of Autocad's (non editable) anonymous blocks.
Not a block, but locked behind a Block,
maybe just what other CADs call a standard "Group" - but non editable.
So no advantage but all disadvanteges combined.
The only useful action I can imagine is EXPLODE (or better XPLODE ?)
"Instances" of "anonymous Blocks" sounds even more scary to me.

Parametric Block sounds much better.
It is more similar to a mixture Plugin Object (e.g. a Window) or a BIM Style
(e.g. a Wall or a Column) that I am used to (e.g. from Vectorworks)
But AFAIK I can change the (given) parameters of the Instances of a
Parametric Block - but still always EDIT that PBlock.
(e.g. change Materials or change all kind of the non parametric parts etc.)

(In VW speech that would be e.g. a "stylized" Window where I dictate mostly
the overall appearance, Layers, Materials, detail Dimensions, ... by Style,
but give allow change-ability basic overall Dimensions and Settings,
(e.g. Number of Sashes, width, height, ...)
To make the inserted Instances as "parametric" as needed.

So I do not (?) really get the meaning of BC's Components (usage) ins standard usage.
Delivered BC Components, e.g. Windows, are usually parametrical.
I chose a e.g. Window, insert it in several positions with parametrized dimensions.
If i later have to change e.g. from aluminum windows to cheaper plastic Windows
i could replace that Component by a similar but more suited Window type ...
(if it would be available)
and it would keep my custom sized "inserted" Windows dimensions (?)
Meaning I could edit a single "stylizing" Component to give all my Window Insertions
a different appearance

Maybe it is different just because of the IFC Import.
Where BC just can make a separate Component of each single Window.
Which, of course, is great - as is as it still looks like in the import source and seems
even still parametric editable.
(did not yet check if it will just scale the whole element as VW does with e.g. RVT imported)