Topic: attribute 'linking'

[Lee Mac]

it appears as though i need to get a lesson on how to post code!!!

Maybe take a visit to the 'First things First' board.

[rooster jk]

it appears as though i need to get a lesson on how to post code!!!

Maybe take a visit to the 'First things First' board.

good idea for sure...

Code: [Select]

(defun c:VOL ()
(vl-load-com)
;;get a reference to model space
(setvar "textsize" 0.09375)
(setvar "luprec" 8)
(setq *model-space*
       (vla-get-ModelSpace
(vla-get-ActiveDocument (vlax-get-acad-object))
       )
)
;;pass this function an entity and a point
(defun Linkedvol (ent pt / obj objID ip width str)
  ;;convert the entity to an object
;;;  (setq obj   (vlax-ename->vla-object ent)
;;; ;;get the object ID
;;; objID (vla-get-objectid obj)

  (setq vl1 (car (entsel "\nSelect Volume Entity: ")))
  (setq objID (vlax-invoke-method (vla-get-Utility (vla-get-activedocument (vlax-get-acad-object))) "GetObjectIdString" (vlax-ename->vla-object vl1) :vlax-False))

  (setq ;;convert the point
ip    (vlax-3D-Point pt)
;;set the width for the MTEXT
width 0.0
  )
;;set the string - this creates the field
;;; str   (strcat
;;; "%<\\AcObjProp Object(%<\\_ObjId "(rtos objID 2 0)">%).Volume \\f \"%lu2%ct6%qcu yd\">%"
;;;       )

  (setq str (strcat "%<\\AcObjProp Object(%<\\_ObjId " objID ">%).Volume \\f \"%lu2%ct6%qf1%pr2 CU YD\">%"))

  ;;Create the MTEXT entity containing the field.
  (vla-addMText *model-space* ip width str)
)

;; Set A = the entity and set B = Point for text
(setq a (car (entsel)) b (getpoint "\n Select Point To Locate Field: "))
;;Call the function
(linkedvol a b)
(princ)
  )


[gile]

I appologise, I thaught it wasn't possible to get the volume of a 3d solid in a field.

[T.Willey]

I appologise, I thaught it wasn't possible to get the volume of a 3d solid in a field.

It doesn't look like you can with the field command, at least in '09 it doesn't show a volume option when picking a 3d solid as an object.  But with code, you can create a field to any property that can be returned with ActiveX.

[rooster jk]

I appologise, I thaught it wasn't possible to get the volume of a 3d solid in a field.

It doesn't look like you can with the field command, at least in '09 it doesn't show a volume option when picking a 3d solid as an object.  But with code, you can create a field to any property that can be returned with ActiveX.

so i have taken the code that Lee linked me to and modified to be able to get a 3dsolid and a mass element volume linked to the attribute. but i'm still having the issue of the 3d solid only giving me the value in cubic inches and the mass elements giving me the value in whatever the volume units of the drawing are set to.  this causes me greif since i need to be able to link both of these objects and have the same output.  so i'm thinking that it's going to involve using a setvar and setting the volume units to cubic inches and then doing math in the lisp to be able to get the output to cubic yards...any thoughts???

[rooster jk]

i should probably say at this point that i'm using Architecture 2011...which is where the mass element stuff comes from.

[Lee Mac]

You can add a conversion factor to the field formatting to convert from cubic inches to cubic yards.

As for the Mass Element - I've never worked with one so I don't know the ObjectName, but I should imagine it would be a case of using an IF statement whilst iterating through the SelectionSet, and if the object is a Solid, use one field code, if a Mass Element, use another.

[rooster jk]

this lets me pick either the 3dsolid or the mass element

Code: [Select]

(and (ssget '((0 . "3dsolid,AEC_MASS_ELEM")))

and i'm sure that from here the conversion isn't that difficult.  but i'm wondering if we can set the volume units of the drawing so that if either are picked the same output happens???

[gile]

It doesn't look like you can with the field command, at least in '09 it doesn't show a volume option when picking a 3d solid as an object.  But with code, you can create a field to any property that can be returned with ActiveX.

Thanks Tim, I didn't know that.
Glad to learn a knew thing.

[ronjonp]

It doesn't look like you can with the field command, at least in '09 it doesn't show a volume option when picking a 3d solid as an object.  But with code, you can create a field to any property that can be returned with ActiveX.

Thanks Tim, I didn't know that.
Glad to learn a knew thing.

X2

[rkmcswain]

A LISP program could certainly be written to create the fields for you following selection of the source object and object to house the field. Here is one such example.

Lee, I was trying a similar exercise myself, but I kept getting #### for the field - so I found this thread and looked at your example code. I'm doing (what I think) is the same thing. How about another set of eyes to look at this code snip?

Code: [Select]

(setq att2obj (vlax-ename->vla-object att2))
(if (> (vl-string-search "x64" (getvar "platform")) 0)
  (progn
    (setq util (vla-get-Utility (vla-get-activedocument (vlax-get-acad-object))))
    (setq objid (vlax-invoke-method util "GetObjectIdString" att2obj :vlax-False))
   )
  (setq objid (rtos oba 2 0))
)
(setq new (strcat "%<\\AcObjProp Object(%<\\_ObjId " objid ">%).Length \\f \"%lu2%pr2\">%"))
(vla-put-TextString att2obj new)

The code runs fine, it inserts the field, but the display of the field is ####
The field string is: %<\AcObjProp Object(%<\_ObjId 8796083683168>%).Length>% , which matches exactly what I get if I manually create the field. What am I overlooking?
TIA

[Lee Mac]

Hi rk,

Assuming the variable 'oba' is defined, your code looks to be correct, though, I personally would write it in the following way:

Code: [Select]

(setq obj (vlax-ename->vla-object att2))
(if (vl-string-search "64" (getenv "PROCESSOR_ARCHITECTURE"))
    (setq id (vla-getobjectidstring (vla-get-utility (vla-get-activedocument (vlax-get-acad-object))) obj :vlax-false))
    (setq id (itoa (vla-get-objectid obj)))
)
(vla-put-textstring obj (strcat "%<\\AcObjProp Object(%<\\_ObjId " id ">%).Length \\f \"%lu2%pr2\">%"))
Note that you may require a Regen to display Fields in some objects (such as attributes).

[irneb]

Note that you may require a Regen to display Fields in some objects (such as attributes).

That's probably the major reason. You could also send a selection of objects to the UpdateField command.

I wonder if it's doing much use if you use the ActiveX Object's Update method on the attribute and/or block - just to not need a full regen and/or command call.