https://community.graphisoft.com/t5/Libraries-objects/Smart-Hotspots/m-p/8054#M50503 <DIV class="actalk-migrated-content">Sheesh, I havent been here in a while and cant believe I missed this post.<BR /><BR />I havent played with the angle editing but the length type is pretty fun. I added a feature to our objects that allow the user to drag the joist and beam labels across the length of the member.<BR /><BR />In the following example, <STRONG>locx</STRONG> is the location of the label along the length of the joist (x-axis), <STRONG>labl_v</STRONG> is a verticle placement either above or below the member. The first hotspot determines a start point, the second creates a vector or direction to move from the start point and the last is the moving point itself. I also borrowed a tip from DNC concerning the unique ID by increasing the number by 1 before each HOTSPOT statement. That way you dont have to keep track of which ID's you have used and it becomes more "Cut &amp; Paste" friendly.<BR /><BR />hsp=hsp+1<BR />HOTSPOT2 0, labl_v, hsp, locx, 1+128 ! base<BR />hsp=hsp+1<BR />HOTSPOT2 -1", labl_v, hsp, locx, 3 ! vector<BR />hsp=hsp+1<BR />HOTSPOT2 locx, labl_v, hsp, locx, 2 !move-able<BR />TEXT2 locx,labl_v,lstr</DIV> Mon, 03 Feb 2025 16:39:25 GMT Anonymous 2025-02-03T16:39:25Z https://community.graphisoft.com/t5/Libraries-objects/Smart-Hotspots/m-p/8054#M50503 <DIV class="actalk-migrated-content">Sheesh, I havent been here in a while and cant believe I missed this post.<BR /><BR />I havent played with the angle editing but the length type is pretty fun. I added a feature to our objects that allow the user to drag the joist and beam labels across the length of the member.<BR /><BR />In the following example, <STRONG>locx</STRONG> is the location of the label along the length of the joist (x-axis), <STRONG>labl_v</STRONG> is a verticle placement either above or below the member. The first hotspot determines a start point, the second creates a vector or direction to move from the start point and the last is the moving point itself. I also borrowed a tip from DNC concerning the unique ID by increasing the number by 1 before each HOTSPOT statement. That way you dont have to keep track of which ID's you have used and it becomes more "Cut &amp; Paste" friendly.<BR /><BR />hsp=hsp+1<BR />HOTSPOT2 0, labl_v, hsp, locx, 1+128 ! base<BR />hsp=hsp+1<BR />HOTSPOT2 -1", labl_v, hsp, locx, 3 ! vector<BR />hsp=hsp+1<BR />HOTSPOT2 locx, labl_v, hsp, locx, 2 !move-able<BR />TEXT2 locx,labl_v,lstr</DIV> Mon, 03 Feb 2025 16:39:25 GMT https://community.graphisoft.com/t5/Libraries-objects/Smart-Hotspots/m-p/8054#M50503 Anonymous 2025-02-03T16:39:25Z