Xdata and Xrecord?
Dietmar Rudolph
in addition to Anders' reply:
You can attach xdata to any AutoCAD object whether it's visible (like
a line) or not (like a layer, or like model space). Xdata is limited
to a small amount of data per object and you need to share this small
amount with all the other applications that use it.
Xrecords may be of arbitrary length and there may be many xrecords per
object (e.g. one per application). You cannot attach xrecords directly
to an object. You first attach an Extension Dictionary to the object,
then you put one or more xrecords into this dictionary.
Dietmar Rudolph
President, CR/LF GmbH, http://www.crlf.de
Vice-President Europe, CADLock, Inc. http://www.cadlock.com
Webmaster, AutoCAD Developers Group Europe, http://www.adge.org
Member of the Autodesk Discussion Forum Moderator Program
Author, "Mastering AutoCAD 2000 Objects", http://www.crlf.de/Verlag/PublishingServices.html
roder
tell any web, qhere I can find more detailed information about this?
"Dietmar Rudolph" <die...@crlf.de> escribió en el mensaje
news:7go5hs4m3vs0u96oi...@4ax.com...
______________ ______ ____ __ _
Javier Lasheras Díaz
Departamento de Estructuras
E.T.S Arquitectura
Universidad de Navarra
jla...@delta.dti.unav.es
Dietmar Rudolph
>tell any web, qhere I can find more detailed information about this?
Javier,
depending on what you want to know just ask here, we'll try to explain
it for you (but ask a bit more specific ;-). If you need a complete
explanation, I can only suggest to read the book I wrote which
explains everything you need to know about this subject. See the URL
below for details.
amy
I am ordering your book now
amy
Dietmar Rudolph wrote in message ...
Tony Tanzillo
about this subject. In fact, there is one very important
difference between Xdata and Xrecords that you, and your
book completely overlook.
Dietmar Rudolph wrote:
>
> >This may be useful for an aplication I'm developing. Can you explain me, or
> >tell any web, qhere I can find more detailed information about this?
>
> Javier,
>
> depending on what you want to know just ask here, we'll try to explain
> it for you (but ask a bit more specific ;-). If you need a complete
> explanation, I can only suggest to read the book I wrote which
> explains everything you need to know about this subject. See the URL
> below for details.
>
> Dietmar Rudolph
>
> President, CR/LF GmbH, http://www.crlf.de
> Vice-President Europe, CADLock, Inc. http://www.cadlock.com
> Webmaster, AutoCAD Developers Group Europe, http://www.adge.org
> Member of the Autodesk Discussion Forum Moderator Program
>
> Author, "Mastering AutoCAD 2000 Objects", http://www.crlf.de/Verlag/PublishingServices.html
--
/*********************************************************/
/* Tony Tanzillo Design Automation Consulting */
/* Programming & Customization for AutoCAD & Compatibles */
/* ----------------------------------------------------- */
/* tony.t...@worldnet.att.net */
/* http://ourworld.compuserve.com/homepages/tonyt */
/*********************************************************/
Dietmar Rudolph
>about this subject. In fact, there is one very important
>difference between Xdata and Xrecords that you, and your
>book completely overlook.
From the book's last page:
"The information in this book should help you to develop your own
applications that work with AutoCAD data. While doing so, you will
probably discover new objects or new procedures. If you do and you
think that others could also benefit from them, drop me a note at
die...@crlf.de".
So yes, I'm aware that there are errata and omissions (and I already
corrected some when preparing the German translation). Would you
please be so kind to tell what you think needs further explanations?
Tony Tanzillo
What I said has nothing to do with any discliamer in
your book, or the fact that it contains errata and
ommissions.
What I said was quite simply, that the statement you
made in your post, is simply not true:
> I can only suggest to read the book I wrote which
> explains everything you need to know about this subject.
You may believe that your book explains 'everyting
you need to know about' this, or any given subject.
A more factually accurate statement would be that
your book explains everything that _you_ know about
the subject.
As far as what you are missing about Xrecords verses
Xdata, it has to do with entity handle/object id
translation within deep clone operations.
To see an example, create two entities. To one of
those entities, attach both Xdata and an extension
dictionary with an Xrecord. In both the xdata and
the Xrecord, store the handle of the other entity.
Then, create a block containing both entities.
Insert the block, and then explode it.
In the resulting copy of the object with the xdata
and xrecord attached that was produced by exploding
the block, compare the value of the entity handle
in object's xdata with the value of the entity handle
in the object's xrecord.
--
Dietmar Rudolph
>In the resulting copy of the object with the xdata
>and xrecord attached that was produced by exploding
>the block, compare the value of the entity handle
>in object's xdata with the value of the entity handle
>in the object's xrecord.
what Tony is referring to is that in the cloned copy of the
referencing entity the xdata handle correctly points to the newly
created copy of the referenced object. This is how a soft pointer link
should work. However in the cloned copy of the xrecord the link still
points to the original copy of the referenced object, even though you
used the 330 group code indicating soft pointership.
Tony is correct in saying that my book should have noted this problem.
I apologize for assuming Autodesk software to work as I think it
should ;-) I've made a note and will add this to the next revision.
BTW: Tony, is it just me or does wblock.arx crash at your side as well
when trying to export the intermediate block to a file?
> You may believe that your book explains 'everyting
> you need to know about' this, or any given subject.
> A more factually accurate statement would be that
> your book explains everything that _you_ know about
> the subject.
I do not think that that would be more factually accurate ;-) I do
believe that if a developer has read my book cover to cover she/he
will indeed know enough about the subject to find out and correct any
problems she/he will run into when interacting with the drawing
database. For most readers this will be 'everything they want to
know'.