archicad-additional-json-commands, please recompile it for AC 26

[_c_]

Hello @Tibor Lorantfy,

I believe this would benefit others too. Would it be possible for you -or anyone- to add the AC 26 version of the archicad-additional-json-commands for both Win and Mac?

I can't install the Xcode on my Mac (hard disk full) and don't have a Visual Studio licence on the Win partition 😟.

Thank you!

[kovacsv]

The same functionality with some extra commands are available as part of the Tapir package. It is compiled to Archicad 25 and 26.

Install instructions: https://github.com/ENZYME-APD/tapir-archicad-automation

Documentation for the additional commands: https://enzyme-apd.github.io/tapir-archicad-automation/archicad-addon

[_c_]

Hello Kovacsv, thank you for your answer,

do you perhaps know which of your Add-ons must be installed, in order to have the Tapir Python extension working? See here, from the above mentioned GitHub page: 

The Archicad Add-on of Poco and Lorantfy are not the same, unfortunately. They rather partly overlap and integrate each other. Notably, Lorantfy has the ReloadLibraries command, which I believe to be vital for GDL scripting, while Poco has the GetBuildingMaterialPhysicalProperties command, which is such a blessing.

Below a comparison as of today. In red the commands unique to each other:

[kovacsv]

I don't know what do you mean by poco's Add-On, I know of only two similar Add-Ons:

1. tlorantfy's Add-On that is no longer maintained as far as I know.
2. Tapir Add-On that is based on tlorantfy's work, and extended with some other functionalities. Some of the commands are not existing yet, the reason behind this is that they need some reconsideration about how they fit in the big picture.

Personally I recommend using the Tapir one since that is actively maintained. If you are missing some commands, you can open an issue here: https://github.com/ENZYME-APD/tapir-archicad-automation/issues

[_c_]

Hello kovacsv,

Tapir is Poco2018 or he is hosting it or maintaining it: https://github.com/poco2018

I'll ask him about the recompilation then.

The ReloadCommand is the next best (and only) feature allowing to use an external editor for GDL without copy-pasting to and fro in the built-in editor. Even so it's quite cumbersome.

I must say, it's not an easy task to get some automatisation done in Archicad 🙂

[_c_]

Hello @poco2013,

which is the add-on of kovacsv that we need to install? (see screenshot hier from GitHub)

Would you have an example of the proper usage of GetBuildingMaterialPhysicalProperties?

It's crashing AC non-stop while I try to fetch the expected material array, it would be good if it just returned an error.

(AC 26 GER demo, on MacOS)

Thank you

[kovacsv]

The Tapir Archicad Add-On is maintaned by ENZYME-APD. I've created an issue for introducing the ReloadLibraries command: https://github.com/ENZYME-APD/tapir-archicad-automation/issues/60

[_c_]

Thank you

[poco2013]

Thank you for bringing this to my attension

I am no longer supporting Archicad's AddOns or the Tapir connection. To avoid any further confusion I have deleted the Tapir fork on my GitHub site. Note, if you have downloaded any files from that site, I recommend that you do not use them and delete them. The apx files were compiled only for windows OS. If you recompiled for Mac, i can not advise as what will happen.-- most likely a exception. However, the exception you described was probably due to not entering a value into the Command handler parameters, Even though those values were not used, a place holder had to be added there or a memory exception would occur. This was indeed a bug, that I did not address because development on my part was suspended. Also the format that I used for the Tapir connection and that used by the Tapir team was in conflict so anything remaining from my code should not be used and deleted. That is why i suspended any further development or maintenance.

I was not aware that my old Tapir fork was still public. Apparently, you can not make a fork private, so -- I have deleted it.

Sorry for the Confusion.

[_c_]

Gerry, very kind of you to clarify.

I will now use the other fork, perhaps that will solve the GetBuildingMaterialPhysicalProperties issue that I am seeing.