Forum Replies Created
-
Posts
-
Hi Daniel,
alas, this is currently not possible. Values calculated by Property Scripts are only accessible for the “old listing”; not accessible by either Schedules, Labels or API.
On a v20/v21 basis, I don’t even have a workaround to suggest. Sorry.
Cheers,
GregHi,
“Custom Pen” is created during operations such as copy/paste and explode (incl. Save as GDL as well), when the appearance of the original element was using a pen that does not exist in the pen table. This can happen if you are using either Graphic Overrides or Renovation Overrides, with a Rule that “overrides pen color only” – which means elements are displayed with lines whose thickness and color are defined by two different pens.
This happens to ensure that the appearance does not change during copy/paste, explode (or Save as GDL for that matter) – wysiwyg behavior.You can avoid creating custom pens by turning off such Overrides before copy/paste, explode, or Save as GDL; or you can modify the pens afterwards. (specifically for Save as GDL, you have to do that in the GDL Editor).
Does this answer your problem? How was the object in question created?
I understand your use of a label, but that is a – known, and for lack of a better solution, accepted – workaround. Normally, it is natural for a label to visible at the time of placement – you would want to see the results instantly, whether they need adjusting or not.
If you are attaching labels to elements for the sole purpose of calculating values, then – at least theoretically – that label should not be a label at all. Practically of course, that’s still the only current way to achieve custom calculated values in schedules, so scheduling labels is still allowed – however counterintuitive that approach is.
The proper solution would be a dedicated calculation object (not a label), that is attached to the element and does the calculations when requested, but not necessarily having any visible symbol on plan. Something like property objects, but available for all outputs (schedules, labels, IFC, you name it). Alas that’s a topic for an unknown future version of ArchiCAD – but because we hope to focus on the correct approach sometime, we’re not planning to improve the existing, dead-end workaround.Cheers,
GregHi,
this type of automatic labeling has been removed from v19 with the introduction of multiple labels per element. While it made some sense to have an option whether an element has a label or not, with multiple labels it would be very complicated, to set “how many labels does this element have, where they are, how do they look, etc.” from the element settings.
Besides, the elements should exist from the early design phase, while labeling elements in most cases only takes place once the design has already settled – so they seldom get created at the same time.
Nevertheless, in v19 we’ve also introduced a function that can place a label on multiple elements with a single click. By default you can find it under Document / Document Extras / Label Selected Elements. This is in a way even easier than the previous method, because it can place labels on different types of elements at the same time (while in previous versions, you had to do it separately for each element type).
Whether to re-introduce an option to label elements upon creation is still under debate. But we believe that automatically labeling all elements is just as problematic as labeling none – you’ll either have to keep deleting unnecessary labels, or keep switching the auto-labeling on/off. The most flexible solution still is to select everything you want labeled, and label them with a single command.
