2021-08-17 08:27 AM - last edited on 2024-09-24 10:30 AM by Doreena Deng
2021-11-25 11:30 AM - edited 2021-11-25 11:31 AM
Hi Peter!
So, I managed to almost figure it out, but there are still some issues. I used the ASSOCLP_PARVALUE to request ac_coords, which in my object are the coordinates of the slab. However, when imported to the label, I only get the coordinates of holes in the slab - see attached screenshot 1. This the code I use:
DIM ac_coords[]
n = REQUEST ("ASSOCLP_PARVALUE", "ac_coords", _unused, type, flags, dim1, dim2, ac_coords)
FOR i=1 TO vardim1(ac_coords)
TEXT2 x,y, ac_coords[i]
y=y-radhojd !Moving text to next row
NEXT i
The coordinates imported also look a bit weird. The 0.0508 (which is the status code meaning end of polygon) comes one coordinate to soon, and the last coordinates do not have a status code at all.
Any idea where the problem might be?
As for the UI... commands, I haven't figured out how to handle the array. My current interface looks like screenshot 2, and all those checkboxes and textboxes are attached to single parameters, which I then translate to arrays in my script. Since every story have five or six different parameters, it becomes a bit cluttered. Can I have the same appearance, but have the inputted text or checked box go straight to the array, and how would i script that?
Thank you!
/Kaj
2021-11-29 09:56 AM
Hi,
with your code I got the contour and the hole of a "Floor Consruction" object correctly. Might there be something in your object that overwrites this parameter?
For the UI, this is an example from the "Wardrobe 02" object:
ui_infield{3} bMirrorLeaf[iPanel], ...