GDL
About building parametric objects with GDL.
SOLVED!

Libpack and folder/file structure (not reading the translation)

I am trying to uderstand how the folder structure translation works. I have created a dummy library with 3 files. All what I need is the folder/file structure change, so I do not need now *.po files, just pathNameTable*.json. I did only INT for the sandboxing.

 

I cannot get it to work, probably some silly mistake.

Loading this folder as a libpack does load it straight without translating the path.

Can anyone help with it? Please

 

12 REPLIES 12

There is instruction, what i miss here - is something I am trying to do myself: a sandbox library that works, and can be edited just to see how the changes apply.

Create a New .libpack from Scratch/Upgrade .lcf to .libpack | GRAPHISOFT GDL Center

 

In the end of the day we both probably need to update the already done libraries to libpack mode (for 28+ versions) and keep the sole lcf for the lower versions, with as small changes as possible to reduce housekeeping.

I have uploaded the working version of your sandbox in my previous reply.

If you have any exact questions or need clarification regarding the process explained in the documentation, I am happy to help. 

 

Wishing you good luck,

Zsuzsi

Thanks a lot,

I missed that in the first read  😞

 

Funny when I added that mysefl it did not work

And as I see the whole guid part is not actually needed, that's easier 🙂 wrong assumption

 

I got it working with VELUX library as a folder, but still cannot do .libpack since objects are password protected in lcf

(https://community.graphisoft.com/t5/GDL/LP-XMLConverter-Libpacks-and-password-protected-objects/m-p/...)

Didn't find the answer?

Check other topics in this Forum

Back to Forum

Read the latest accepted solutions!

Accepted Solutions

Start a new conversation!