Forum General discussions About this site Problems and solutions in GDL Forum rules and functions

[Gergely Fehér]

I checked the libdevtoolkit v17, and there are all the subtypes in Sources/ACPM/ArchiCAD/RINT folder. You can compile this with Sources/ArchiCADLibrary/Make/MakeLibrary.pl script, and then use the binaries from the compiled ACPM folder as an additional lib.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

6ACDA889-69B2-4EC5-936C-CB1DA7032A92 is the main ID of the opening subtype. Did you add the proper built-in library as additional lib? In the libdevtoolkit package it is included to the build system…

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

Kristian,

I said there is no solution in GDL Editor, it is true. But for this problem, there is a much better, safer solution with using the lpxmlconverter. Setting the defaults for a complex library should be always done from source, professional GDL development can not be done without that, sorry. You simply do not have enough control on your objects without the source format and the checking/finalizing functions of the converter.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

Barry,

There is no solution for that without the GLOB_CONTEXT in the GDL editor. That’s why I told you about the other solution, with the lp_xmlconverter. Use it, it’s a great tool for developers, many things are much easier with it.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

I thought it is about a window, so my example was the 3d of a window… In labels I think there is no proper way to determine the connection between inside-outside and the reference line. That’s why there is an option in skin list label to reverse the order: from the GDL side you can’t get enough specific information, but the user can easily swap with the order to fit the wall.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

I think that a separate context for the editor is not needed: in your example the “flag” parameter should be deleted. It is a much better solution to use the source format of library parts, and modify parameter defaults with the lp_xmlconverter, during the library compilation. In this case, you should force your category parameters default to an empty string with a replacement definition file, and check that value instead of having one more parameter for checking if the default is set.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

Possible workarounds:

• create and place your object as a wall accessory, then you can “leave out” the doors and windows, so your object won’t override the openings.
• place blocks to your openings, cut your object with this blocks with SEO, and then then use SEO with the cut object and the wall

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

I made a quick test object for that, please paste the next code to a new window’s 3d script:

addz 0.3

define style "aa" "Arial", 300, 7, 0
set style "aa"

material WALL_MAT_A

addy b/2
text 0.5, 0, WALL_MAT_A
del 1

It shows that WALL_MAT_A is the material of the wall towards the positive “Z” direction of the window.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

There is no replacement for that, GDL Editor’s context can not be described with the new globals. Can you tell me a situation why do you need that?

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

Ben, it is the purpose of GLOB_SCRIPT_TYPE: it enables you to write script parts to the master, which will be used in only selected scripts.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

Shaun,
Quick answers:
1. GLOB_SCRIPT_TYPE is ok in the master script.
2. Line numbers: check script should show all errors and warnings. If you send me a file, I can check it, if there is a bug…
3. FAQ: I clicked on your link, and it is working normally. Maybe it could be a temporary server problem…

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

There are 2 problems in your script:
1. If the values of _wh1y and _wh1[1][2] is not equal, then your hotspots are not inline, so editing can not work. Use the same 2nd coordinates in all lines.
2. You shouldn’t put “_wh1[1][1]” in quotation marks, delete them.

Besides these, starting parameter names with underscore is not recommended.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

I think the easiest way to test forward migration is to have 2 ARCHICADs open at the same time: one with the old libraries and one with the new ones. Then I can simply place objects from the old library, and then copy-paste them to the other ARCHICAD with the newer libparts. If they are replaced during the paste, then forward migration is ok.
It’s quite fast, there are no problems with library reloading, and you can check visually the 2 different versions.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

For the first view: you shouldn’t comment the following lines:
! actualGUID = "29BC0A02-02ED-4536-A043-ECE303A3FB31"
Delete the exclamation mark, as you need to set your migration ID to the ID of your new object. In my quick test file, it solved the problem.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

Unfortunately only the standard image and document and zip files can be uploaded, no gsm and lcf from the forum. I’ll check your files soon.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Author]

Posts