2025-10-09 04:08 PM
So now that is has been out for over a year, I am thinking hard about going full gas into use of the keynote feature. The trouble is, so much of our template also uses classifications and properties that are baked into elements or revised on the fly, but still displayed elsewhere in the form of schedules and/or labels. I started to put together a document to outline when it is appropriate to use keynotes vs properties. I also need to outline what information should be displayed using a keynote at different scales, but that is a different discussion. I am curious how others are resolving this feature that is not very BIM, but feels very handy. Any thoughts? Attaching my progress on keynoting rules here.
Operating system used: Mac Apple Silicon 26 Tahoe
3 weeks ago
I agree that things are developed to 'good enough' and rarely see further development.
2 weeks ago
@Erwin Edel schrieb:
I agree that things are developed to 'good enough'...
I disagree! 🤣
2 weeks ago
You'll see, everything will be solved, this too... But only in AC31, or later, when only the subscription model will work. Anyone who stops at AC30 will not be able to use it
2 weeks ago
Then, in Archicad 32, there´s no reason to continue updating the program, as everyone has now lost the luxury of stop paying. Back to just good enough 😅
2 weeks ago - last edited 2 weeks ago
Hi @Davor P
Thanks for that thread to go on.
With this, we have created an Excel file with the following 3-column format:
| COD | _-_ | Full description | _-_ | Budget item | _-_ |
We copy and paste everything from Excel to a project info property. We have created one for each category of element: walls, flooring, ceilings, furniture, etc.
We continue to maintain composites, complex profiles, and surfaces with the following format:
| COD | _-_ | Short description |
Finally, some SPLIT expression properties search for that code and return what they find to the right of it (full description).
This way, we can maintain long descriptions, respect line breaks in the source text, and link them to elements in the model.
We use the same method to assign the starting code to each element directly from Excel.
This way, we don't need to reserve all the elements to modify their description or starting code.
Translated with DeepL.com (free version)
2 weeks ago
Glad it worked! Project info has been my go to solution for site area calcs - put the overall site area in there and call it to calculate percentages with zone areas.