style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"bruceclement" <Tell
href="mailto:bruce@architecturalimaging.com">bruce@architecturalimaging.com>
wrote in message
href="news:f0799b8.-1@WebX.maYIadrTaRb">news:f0799b8.-1@WebX.maYIadrTaRb...
me it ain't so:
1. I can't insert my door tags if my doors are in an xref
(or nested xref).
2. I can't place my door tags in paper space if my doors
are in model space.
3. I can't put my schedule in paper space if my door
tags are in model space.
FWIW, my doors must exist in xrefs and nested
xrefs (e.i. unit plans and common corridors); my tags *should* be in paper
space with my other notes and dims; and my schedule *really should* be in
paper space with the title block, general notes and symbol legend; my tags and
schedule must NOT be in my base plan xref for obvious reasons!
Thanks.
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"bruceclement" <Matt,
href="mailto:bruce@architecturalimaging.com">bruce@architecturalimaging.com>
wrote in message
href="news:f0799b8.1@WebX.maYIadrTaRb">news:f0799b8.1@WebX.maYIadrTaRb...
that's one hell of a workaround: custom blocks, "property sets," non-plotting
data, tags carried into every sheet the plan is xrefed into, manual
cross-referencing - you're breaking rules of good cadmanship all over the
place. And still you have not solved the problem of putting the schedule in
paper space when the xref is in model space.
You asked, "How much of the schedule functionality of
the stock tags is
dependent upon a tag anchor being present...?" The answer is ALL OF IT! Isn't
that the whole point of ADT schedules? Are these new intelligent object
features is in direct conflict with basic features like Xrefs and
Pspace?
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"bruceclement" <Matt,
href="mailto:bruce@architecturalimaging.com">bruce@architecturalimaging.com>
wrote in message
href="news:f0799b8.1@WebX.maYIadrTaRb">news:f0799b8.1@WebX.maYIadrTaRb...
that's one hell of a workaround: custom blocks, "property sets," non-plotting
data, tags carried into every sheet the plan is xrefed into, manual
cross-referencing - you're breaking rules of good cadmanship all over the
place. And still you have not solved the problem of putting the schedule in
paper space when the xref is in model space.
You asked, "How much of the schedule functionality of
the stock tags is
dependent upon a tag anchor being present...?" The answer is ALL OF IT! Isn't
that the whole point of ADT schedules? Are these new intelligent object
features is in direct conflict with basic features like Xrefs and
Pspace?
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Reid M. Addis" <
href="mailto:raddis@addiscomputer.com">raddis@addiscomputer.com> wrote
in message
href="news:C38EDF1BBF3C4B82B74DB3BFF3CF5A81@in.WebX.maYIadrTaRb">news:C38EDF1BBF3C4B82B74DB3BFF3C......
Answers to
"Tell me it ain't so:"
1. I can't
insert my door tags if my doors are in an xref (or nested xref).
Answer: It's
so....but! Hopefully in ADT4.0 this will be "improved"
2. I can't
place my door tags in paper space if my doors are in model space.
Answer: see 1 above
3. I can't
put my schedule in paper space if my door tags are in model space.
Answer: see 1 above. I
actually thought I had a clever answer to this one. Create the schedule in
modelspace then use the Express tools CHSPACE command to move it to
paperspace, but all this weird stuff comes with. It's on the A-DOOR layer so
if you freeze it, you lose your doors in modelspace. However, you can change
these objects (what ARE they Autodesk??) to a different layer then freeze or
turn off that layer. To update, you have to transfer everything back to
modelspace.
Yeah, it's really lame. I know it's easy for us
out here to say "Why doesn't Autodesk hire people with real world experience",
but in fact many of the great programmers are from the world of practicing
architects. This stuff is probably pretty tricky to program. However, the old
Details module allows you to annotate xref objects with xdata on it, so I know
these guys can do it! You could place it in the Wishlist newsgroup, but
Autodesk already knows they need to make this work....soon.
Of course, my answers could be entirely wrong, so
I'll keep an eye on this thread.
--
Regards
------------
Reid M. Addis
Addis Computer
Consultants
1-800-841-4418
href="http://www.addiscomputer.com">http://www.addiscomputer.com
href="mailto:raddis@addiscomputer.com">raddis@addiscomputer.com
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"bruceclement" <Tell
href="mailto:bruce@architecturalimaging.com">bruce@architecturalimaging.com>
wrote in message
href="news:f0799b8.-1@WebX.maYIadrTaRb">news:f0799b8.-1@WebX.maYIadrTaRb...
me it ain't so:
1. I can't insert my door tags if my doors are in an
xref (or nested xref).
2. I can't place my door tags in paper space if
my doors are in model space.
3. I can't put my schedule in paper space
if my door tags are in model space.
FWIW, my doors must exist in xrefs
and nested xrefs (e.i. unit plans and common corridors); my tags *should* be
in paper space with my other notes and dims; and my schedule *really should*
be in paper space with the title block, general notes and symbol legend; my
tags and schedule must NOT be in my base plan xref for obvious reasons!
Thanks.
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Corey A. Layton" <
href="mailto:clayton@bckpc.com">clayton@bckpc.com> wrote in message
href="news:4DED8A499674CA6489DAF8453A9F0F54@in.WebX.maYIadrTaRb">news:4DED8A499674CA6489DAF8453A9......
I'll chime in and agree with you,
Bruce.
The point of using ADT objects w/ attached
schedule data and anchored tags compiled in a schedule is that the data is
RELATIONAL. As soon as someone uses the word "manual" when describing a
seemingly nifty "workaround", just walk away.
One thing that I've learned is that when you
travel down the road of forcing the software to accomplish something that it
was not designed to do (i.e. "workaround"), the path becomes darker and more
treacherous; until you fall into a great pit of frustration.
You can only bend so much before you
break!
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"bruceclement" <Matt,
href="mailto:bruce@architecturalimaging.com">bruce@architecturalimaging.com>
wrote in message
href="news:f0799b8.1@WebX.maYIadrTaRb">news:f0799b8.1@WebX.maYIadrTaRb...
that's one hell of a workaround: custom blocks, "property sets,"
non-plotting data, tags carried into every sheet the plan is xrefed into,
manual cross-referencing - you're breaking rules of good cadmanship all over
the place. And still you have not solved the problem of putting the schedule
in paper space when the xref is in model space.
You asked, "How much of the schedule functionality of
the stock tags
is dependent upon a tag anchor being present...?" The answer is ALL OF IT!
Isn't that the whole point of ADT schedules? Are these new intelligent
object features is in direct conflict with basic features like Xrefs and
Pspace?