Managing embedded library parts

[Stig Bengtsson]

The ability to embed library parts was a great new feature in 13 but the current implementation is far from perfect:

a, When creating and embedding a new library part you can't see the content of the embedded library when you are in the "save library part" dialogue. A list of the already embedded parts is helpful if you want to replace an earlier version of an object and need to know the exact name to overwrite.

b, When saving a new part one has to click on "options" to make sure the format is editable GDL and not binary. A step easily forgotten, but the mistake becomes apparent when the project file size sky-rockets. In earlier versions the choice between editable GDL and binary was not hidden behind an options button and therefor easily monitored.

c, There is no way to find out which of the embedded objects are actually placed in the project. In earlier versions saving a .pla would extract all the placed library parts into a folder. In AC13 the embedded parts remain embedded wether placed or not when the project is saved as a .pla. The library manager needs to show if an embedded object is placed, similar to how the hotlink manager shows placed hotlinks.

Stig

[Rafal SLEK]

Stig wrote:
a, When creating and embedding a new library part you can't see the content of the embedded library when you are in the "save library part" dialogue. A list of the already embedded parts is helpful if you want to replace an earlier version of an object and need to know the exact name to overwrite.

You are right. It is good that after saving name could be easily changed via Library manager. At least.

Stig wrote:
b, When saving a new part one has to click on "options" to make sure the format is editable GDL and not binary. A step easily forgotten, but the mistake becomes apparent when the project file size sky-rockets. In earlier versions the choice between editable GDL and binary was not hidden behind an options button and therefor easily monitored.

You are right. But in my opinion it should be switched by default to "Editable GDL Script" - Binary 3D data is almost unused. No need to unhide these from Option button.

[Stig Bengtsson]

Rafal wrote:

Stig wrote:
b, When saving a new part one has to click on "options" to make sure the format is editable GDL and not binary. A step easily forgotten, but the mistake becomes apparent when the project file size sky-rockets. In earlier versions the choice between editable GDL and binary was not hidden behind an options button and therefor easily monitored.

You are right. But in my opinion it should be switched by default to "Editable GDL Script" - Binary 3D data is almost unused. No need to unhide these from Option button.

I have found that the default sometimes reverts to Binary in Teamwork projects. If you don't open the options menu to check you can create a 25Mb "Binary" object by mistake instead of a 25Kb "Editable GDL Script" object. Place 10 of those in a project and you have 250 extra Mb embedded in your file.

Stig

[ztaskai]

Stig wrote:
a, When creating and embedding a new library part you can't see the content of the embedded library ...

Good point. I'll add it to our issue tracking system and start a conversation about it with the product designer of this function.

Stig wrote:
b, When saving a new part one has to click on "options" to make sure the format is editable GDL and not binary...

I guess it happened when standardizing the file dialogs for more conformity with the native OS dialogs. It is interesting nonetheless. I just let the designated product designer know about your opinion.

Stig wrote:
c, There is no way to find out which of the embedded objects are actually placed in the project...

Totally agree. This information is available in the Library Manager from AC14 on.

Best regards,

[Erika Epstein]

ztaskai wrote:

Stig wrote:

Stig wrote:
b, When saving a new part one has to click on "options" to make sure the format is editable GDL and not binary...

I guess it happened when standardizing the file dialogs for more conformity with the native OS dialogs. It is interesting nonetheless. I just let the designated product designer know about your opinion.
quote]

I filed a bug report on this recently.