2012-01-3006:44 AM - last edited on 2023-05-2412:36 PM by Rubia Torres
2012-01-3006:44 AM
I have a window tool that has been scripted, from long ago but it has been updated accordingly throughout the years. (I personally did not create the window but have over the last few years gotten familiar with it's script and done modifications of my own).
Since getting Archicad 15 certain facets of the window no longer work.
The window operates on wallhole command. Obviously there is a wall hole associated the 'A' and 'B' dimensions.
The problem occurs when we want to add a high lite or fan lite or sill. When these options are selected (in AC14) wall holes are added to fit the shape of the fan lite, high lite or sill.
From here Prism_ commands are used to create the sill, etc... as well as replace parts of the wall that have been removed by the additional wallhole commands.
In AC15 these additional wallhole commands are not recognised and the added sill or fan lite sits "inside the wall.
Is there any reason for this?
Can it be fixed or adjusted?
Has the command been omitted?
Is there another command I can use to replace the wallhole commands?
I don't know of any changes to the WallHole command, and I have not seen this issue with my own library parts. My guess is a missing macro or other scripting issue. The easiest way for others to look at this is to post the object here.
David
David Maudlin / Architect www.davidmaudlin.com Digital Architecture AC27 USA • iMac 27" 4.0GHz Quad-core i7 OSX11 | 24 gb ram • MacBook Pro M3 Pro | 36 gb ram OSX14
It's definitely a scripting issue I just loaded a previous version of the library which contains no script editing on my behalf and all of the associated macros, some of which I have edited.
Which lead to this question.
Is any one aware of any specific script that could negate a wall hole command?
Really it could be any thing, even a "DEL TOP" that unknowingly overwrites a a "ROT" command.
Let me know, what kind of ArchiCAD you use (INT,USA,GER...) or upload here the windows, which works wrong. I can check it and find the problem, if I get the object. On the other hand the wallhole command is the same as before, but some of the Window base macro has been changed deeply, so it can cause a problem...
But I mentioned I loaded on of the first versions that I owned (around AC-13)
and it worked fine. Only I have made script changes since then to the window and it's macros. Now the plan is to load the current window and older (unedited) versions of the associated macros.
As a footnote I am relatively novice at scripting and have taught myself from the cookbook and studying script structure of objects I have.
So it is very possible I have changed something with realizing the implications of that change.
Hi Shingleback
If it's an old essential library window, the fix requires disabling the Panel_infill.gsm macro call. I haven't looked much further into this as I had abandoned commercial development of the Essential library years ago and only fix / make objects to suit my own needs these days.