We value your input!
Please participate in Archicad 28 Home Screen and Tooltips/Quick Tutorials survey

Libraries & objects
About Archicad and BIMcloud libraries, their management and migration, objects and other library parts, etc.

Auto Labels selection V17

I have notice when trying to select my (cadswift) Auto Labels in v17 I have to hover over them for a few seconds before I can actually select them.
This is not an issue with the ArchiCAD Auto Labels and I have tried recreating my labels in v17 but the result is the same.
I have also searched the code for the ArchiCAD labels but can't find anything pertaining to this issue, though i may simply have missed it.
Any ideas?
Creator of Cadswift's parametric GDL libraries
Creator of Infinite Openings and Component Catalogues
Push the envelope & watch it bend
website: https://cadswift.com.au/
YouTube: https://www.youtube.com/user/CADSwift/playlists
3 REPLIES 3
Anonymous
Not applicable
Hey mate

What have you got going on in your master script?
I had one that was hanging a little, that was calling wall heights and then doing a little math, then pushing to the 2D script.
Is your label attached to anything linked to story heights?
Kristian (my brother from another mother),

Good to hear from you.
I think you may have touch on the issue; its an opening label that reads the story, ID, opening size, and relational zone data from the window/door. I just tested my wall label and it can be selected immediately though it also reads a variety of data. I might try stripping out the possible data from the opening label and see if that indicates what causes the issue.

Cheers mate,
Creator of Cadswift's parametric GDL libraries
Creator of Infinite Openings and Component Catalogues
Push the envelope & watch it bend
website: https://cadswift.com.au/
YouTube: https://www.youtube.com/user/CADSwift/playlists
Anonymous
Not applicable
Yeah mate the openings could be a few layers too.
If the window is linked to head height and the wall is linked to storey!
If it still plays up maybe try isolate it with a one run loop.
Or kick it off with a GLOB_MODPAR perhaps.