The 1001 key... Ahhhh, the missing link... I see said the blind man. Thanks
so much Bobby.
Have a great weekend.
--
Phillip
"Bobby C. Jones" wrote in message
news:3369DA7E3B1236028563BA4D5C766691@in.WebX.maYIadrTaRb...
> Hello Phillip,
> Time is short these days, but I'll see if I can help shed some light. The
> vlaObj argument expects an ActiveX object. Visual LISP provides you a
> simple way to convert entity names into ActiveX objects with the
> (vlax-ename->vla-object ...) function:
>
> (setq vpEntity (car (entsel "Select a floating viewport: "))
> vla:vpEntity (vlax-ename->vla-object vpEntity))
>
> If you successfully select a floating viewport, vla:vpEntity will contain
a
> reference to your ActiveX viewport object. Feed it to ax:GetXdata and
> observe what it returns:
>
> (ax:GetXdata vla:vpEntity "ACAD")
>
> Returns something similar to this:
>
> ((1001 . "ACAD")
> (1000 . "MVIEW")
> (1002 . "{")
> (1070 . 16)
> (1010 0.0 0.0 0.0)
> (1010 0.0 0.0 1.0)
> (1040 . 0.0)
> (1040 . 1384.78)
>
> (1002 . "{")
> (1003 . "A-Area-Bdry")
>
> (1003 . "S-Roof-Trus")
> (1002 . "}")
> (1002 . "}")
> )
>
> Notice that the 1001 key contains the AppID. This is how you will need to
> structure your xdata list to feed to ax:PutXdata. Be careful here!
Unlike
> the LISP method for storing xdata on an object, the ActiveX method will
> automatically register your AppID if it's not already. A misspelled AppID
> could cause you a lot of grief later.
>
> I showed you one simple method of obtaining an ActiveX object. There are
> others and the whole topic of Visual LISP's implementation of ActiveX is a
> very broad topic. If you have other questions please ask. There are many
> in this group whom are willing and more than able to help. Good luck.
> --
> Bobby C. Jones
> www.AcadX.com
>
>
>