Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
I think that object id is not constant, because after each autocad relaunching it changes.
Is there some way to find unique number or the name of the object?
> Most of us are already familar with and tired of that , which
> often results in drawings containing thousands of APPIDS that slow
> down the lookup of any APPID, not to mention slow down saves and
> loads and reading of any XDATA.
One AppID with different string values will suffice.
Terry
Edited by: Discussion_Admin on May 29, 2009 10:33 AM
And will that code carry along and fire when someone merges the drawing
data in LT or another AutoCAD workalike?
{quote}
No, it won't. It also won't work in Microstation, IntelliCAD, or the dozen
or so other apps which the data could be opened and edited with.
But, Yours does not work at all...... period
Your idea doesn't work in AutoCAD and it doesn't work in LT, without
imposing unreasonable restrictions on a user (e.g., they can't copy the
tagged objects, and have to contend with additional 'baggage' data they
don't need to begin with).
Your idea doesn't work because a user can COPY objects with your so-called
'unique' tag attached to them, which results in the 'unique' tag being
duplicated in multiple objects, and because you and your code are clueless
with regards to how to deal with that (yes there is a way to deal with it,
but that requires ObjectARX).
The fact that you seem to think imposing those kind of restrictions on a
user is acceptable, or means that your kludges actually work, only
demonstrates the way you go about things.
You claim these 'work', because you define 'work'
with a footnote that reads something like: 'as long as you don't do things
like COPY, or use any other command that duplicates objects'.
These are not required when using API we
discuss here,
In a nutshell, you use and advocate these , only
becuase you're not able to use the tools that make them unnecessary, and
allows us to do things the right way and without punishing end users by
needlessly burdening them with extra 'baggage' data they don't need, and/or
restricting them from using certain common commands.
.
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2009
Supporting AutoCAD 2000 through 2009