Announcements
IMPORTANT. Forum in Read Only mode. You can no longer submit new questions or replies. Please read this message for details
Autodesk Architectural Desktop 2007 & Prior
Welcome to Autodesk’s Autodesk Architectural Desktop 2007 & Prior Forums. Share your knowledge, ask questions, and explore popular Autodesk Architectural Desktop 2007 & Prior topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

TMIAS: Door Schedules using PSpace/Xrefs?

18 REPLIES 18
Reply
Message 1 of 19
Anonymous
243 Views, 18 Replies

TMIAS: Door Schedules using PSpace/Xrefs?

Tell 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.
18 REPLIES 18
Message 2 of 19
Anonymous
in reply to: Anonymous

OK... this issue comes up more and more, and I agree - I common standard is
NO ANNOTATION IN BASE DRAWINGS, and I can think of a bunch of reasons why
someone would want to hold to that standard.

Step back from it for a minute. How much of the schedule functionality of
the stock tags is dependent upon a tag anchor being present (in other
words - the ability to automatically reflect the door number, for example)?

If you can get past that, and come to the decision that maybe THAT
particular aspect of the scheduling and tags in ADT is not that critical,
then read on. Think about it for a bit, and decide...

.
.
.

Still thinking??? OK... I'll wait...
.
.
.
.
Still here? Good...

What about NOT having tags that automatically reflect the door number? Make
them a simple, dumb, 2D block with an attribute that is keyed to your layer
key style.

Now, attach the property sets to your doors and windows (and if you're using
style-based property sets with style-based default values, most of the data
is already there - you just have to assign the object-based property set for
the door number, window number, etc.). The data is there for the schedule,
but there are no tags.

XREF your drawing into your plot sheet. In paper space, place your 2D tags,
providing the correct numbers as attribute values. The issue that arises
here is that you don't KNOW, by looking at the door, for example, what the
number is. The property is invisible. To deal with that, use the door and
window tags of ADT (or one similar) IN THE BASE DRAWING to show you what the
number is. Set up your layer standard so that those tags come in on a layer
that is set to a no-plot status. So you never see them on the plot, but you
have them as a cross-reference to ensure that your dumb 2D simple-block tags
in the plot sheet have the correct attribute value assigned to them.

--
----------------------------------------------------------------------------
--------
Please do not email me privately with technical issues
----------------------------------------------------------------------------
--------

Matt Dillon
Assistant Moderator: Autodesk Discussion Forums

http://www.dccadd.com


"bruceclement" wrote in message
news:f0799b8.-1@WebX.maYIadrTaRb...
Tell 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.
Message 3 of 19
Anonymous
in reply to: Anonymous

Matt, 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?
Message 4 of 19
Anonymous
in reply to: Anonymous

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.



style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
Tell
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.

Message 5 of 19
Anonymous
in reply to: Anonymous

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">
Matt,
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?

Message 6 of 19
Anonymous
in reply to: Anonymous

Xref the plan into PAPERSPACE (scale it down) to
generate schedule in paperspace (I think you can xref the same drawing twice).
But yeah, Matt is on drugs today <G>. Probably all that hot weather then
rain in Texas!



style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
Matt,
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?

Message 7 of 19
Anonymous
in reply to: Anonymous

Reid,

Your solution may work for paperspace/modelspace issues, but it doesn't
address the very common issue of not putting any annotation in a base
drawing that is going to be XREF'ed elsewhere.

--
----------------------------------------------------------------------------
--------
Please do not email me privately with technical issues
----------------------------------------------------------------------------
--------

Matt Dillon
Assistant Moderator: Autodesk Discussion Forums

http://www.dccadd.com


"Reid M. Addis" wrote in message
news:BF39BB32A3C40E7952753AF03A4E1A92@in.WebX.maYIadrTaRb...
Xref the plan into PAPERSPACE (scale it down) to generate schedule in
paperspace (I think you can xref the same drawing twice). But yeah, Matt is
on drugs today . Probably all that hot weather then rain in Texas!

--
Regards
------------
Reid M. Addis
Addis Computer Consultants
1-800-841-4418
http://www.addiscomputer.com
raddis@addiscomputer.com
"bruceclement" wrote in message
news:f0799b8.1@WebX.maYIadrTaRb...
Matt, 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?
Message 8 of 19
Anonymous
in reply to: Anonymous

First, Bruce, if you are going to use the content and schedule styles that
are provided for ADT out of the box, and do not intend to customize them for
your own purposes, then my workaround is certianly not acceptable.

If, however, you are finding that you need to do some customization, then
maybe it is. It's really not as convoluted as my explanation made it seem.
It simply means using a different property set than that which is provided,
and perhaps a different schedule style. If you understand schedule styles
and property sets, and know what you want, you can do that in a relatively
short amount of time. Less than an hour or so.

Custom blocks and attributes shouldn't be a big deal. That's basic AutoCAD
stuff.

Putting the stock door and window tags on a no-plot layer takes about 5
seconds of editing in the layer key style.

Yes, it does lead to the possibility of errors if the 2D blocks aren't
crosschecked against the anchored tags, and if that's an issue, then the
automatic tags are necessary for you, and as I said in my original post,
then don't read any further. This solution is not for you.

But the fact remains - you cannot tag a door that is xreffed in another file
using the door and window tags currently available in out-of-the box ADT. I
question the validity of basing the use of schedules in general on that one
feature. Until the ability to apply tag anchors to XREF'ed objects is
available, if you see that as a barrier to the use of schedules at all in
ADT, what do you intend to do otherwise that would be better?

Your original post states:

"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!"

My workaround allows for all of that.

--
----------------------------------------------------------------------------
--------
Please do not email me privately with technical issues
----------------------------------------------------------------------------
--------

Matt Dillon
Assistant Moderator: Autodesk Discussion Forums

http://www.dccadd.com


"bruceclement" wrote in message
news:f0799b8.1@WebX.maYIadrTaRb...
Matt, 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?
Message 9 of 19
Anonymous
in reply to: Anonymous

Correction...

My workaround does not allow for the placement of the schedule in paperspace
with the model in model space. THAT, to my knowledge, is not possible. The
scheduled objects and the schedule must exist in the same space.

--
----------------------------------------------------------------------------
--------
Please do not email me privately with technical issues
----------------------------------------------------------------------------
--------

Matt Dillon
Assistant Moderator: Autodesk Discussion Forums

http://www.dccadd.com


"Matt Dillon" wrote in message
news:AA49E9256A917286A00D3A9CE60CA00E@in.WebX.maYIadrTaRb...
>
> "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!"
>
> My workaround allows for all of that.
>
Message 10 of 19
Anonymous
in reply to: Anonymous

Reid,

 

Attaching tags to xref objects is definately on the
wish list as are other xref issues. Please keep posting those things that are
'near and dear' to the Wishes NG.


Thanks,

Dennis McNeal
Autodesk
Building Industry Division


style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">

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.



style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
Tell
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.

Message 11 of 19
Anonymous
in reply to: Anonymous

Yeah, but I was only answering the "How to get a Schedule in Paperspace when
your XREF is in Modelspace". Answer: Xref it twice. I wasn't trying your
overall solution which, in all honesty, would be a NIGHTMARE for users as
well as managers. I received an email today from a fellow manager (your
secret is safe with me) who had to send an email reminder to his CAD users
to be careful of throwing in the garbage plotter parts when changing paper
(probably the thingy that keeps HP paper on the tube). Do you REALLY THINK
these people would be capable of using your method??


I'm waiting.................




Still there??..............

--
Regards
------------
Reid M. Addis
Addis Computer Consultants
1-800-841-4418
http://www.addiscomputer.com
raddis@addiscomputer.com
"Matt Dillon" wrote in message
news:4C0D93BF76E5BF227EA9CB96CB75EC3D@in.WebX.maYIadrTaRb...
> Reid,
>
> Your solution may work for paperspace/modelspace issues, but it doesn't
> address the very common issue of not putting any annotation in a base
> drawing that is going to be XREF'ed elsewhere.
>
> --
> --------------------------------------------------------------------------
--
> --------
> Please do not email me privately with technical issues
> --------------------------------------------------------------------------
--
> --------
>
> Matt Dillon
> Assistant Moderator: Autodesk Discussion Forums
>
> http://www.dccadd.com
>
>
> "Reid M. Addis" wrote in message
> news:BF39BB32A3C40E7952753AF03A4E1A92@in.WebX.maYIadrTaRb...
> Xref the plan into PAPERSPACE (scale it down) to generate schedule in
> paperspace (I think you can xref the same drawing twice). But yeah, Matt
is
> on drugs today . Probably all that hot weather then rain in Texas!
>
> --
> Regards
> ------------
> Reid M. Addis
> Addis Computer Consultants
> 1-800-841-4418
> http://www.addiscomputer.com
> raddis@addiscomputer.com
> "bruceclement" wrote in message
> news:f0799b8.1@WebX.maYIadrTaRb...
> Matt, 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?
>
>
Message 12 of 19
Anonymous
in reply to: Anonymous

Nope, and they probably wouldn't be able to find the command to place the
schedule in the first place, either, let alone get to paper space to deal
with it.

--
----------------------------------------------------------------------------
--------
Please do not email me privately with technical issues
----------------------------------------------------------------------------
--------

Matt Dillon
Assistant Moderator: Autodesk Discussion Forums

http://www.dccadd.com


"Reid M. Addis" wrote in message
news:1B2D5CAC7EBD2B2ADE86773A585A3B83@in.WebX.maYIadrTaRb...

>Do you REALLY THINK
> these people would be capable of using your method??
Message 13 of 19
Anonymous
in reply to: Anonymous

EXACTLY!
I don't know. Is it me or is the stuff under what Salman Rushdie(sp?) called
P2C2E (Processes Too Complicated To Explain)?

Oh well, now where was I? Oh yeah....what is this funny looking red
circle......

--
Regards
------------
Reid M. Addis
Addis Computer Consultants
1-800-841-4418
http://www.addiscomputer.com
raddis@addiscomputer.com
"Matt Dillon" wrote in message
news:4D9F18C1CC0AC0BB46C28BE310A1F853@in.WebX.maYIadrTaRb...
> Nope, and they probably wouldn't be able to find the command to place the
> schedule in the first place, either, let alone get to paper space to deal
> with it.
>
> --
> --------------------------------------------------------------------------
--
> --------
> Please do not email me privately with technical issues
> --------------------------------------------------------------------------
--
> --------
>
> Matt Dillon
> Assistant Moderator: Autodesk Discussion Forums
>
> http://www.dccadd.com
>
>
> "Reid M. Addis" wrote in message
> news:1B2D5CAC7EBD2B2ADE86773A585A3B83@in.WebX.maYIadrTaRb...
>
> >Do you REALLY THINK
> > these people would be capable of using your method??
>
>
>
Message 14 of 19
Anonymous
in reply to: Anonymous

hope you guys are having fun.

--
-------------------------------------------------------------------------
Rob Starz
Plogv 3.0 & 2000 (plot logging) for r14 & 2000
***Enhancement Tools for Arch. Desktop *****
!!!! DormerX out in Sept !!!!
http://www.stardsign.com/main.htm
"Reid M. Addis" wrote in message
news:F27F4D60B724B81BCD96A24F9B7E363E@in.WebX.maYIadrTaRb...
> EXACTLY!
> I don't know. Is it me or is the stuff under what Salman Rushdie(sp?)
called
> P2C2E (Processes Too Complicated To Explain)?
>
> Oh well, now where was I? Oh yeah....what is this funny looking red
> circle......
>
> --
> Regards
> ------------
> Reid M. Addis
> Addis Computer Consultants
> 1-800-841-4418
> http://www.addiscomputer.com
> raddis@addiscomputer.com
> "Matt Dillon" wrote in message
> news:4D9F18C1CC0AC0BB46C28BE310A1F853@in.WebX.maYIadrTaRb...
> > Nope, and they probably wouldn't be able to find the command to place
the
> > schedule in the first place, either, let alone get to paper space to
deal
> > with it.
> >
> > --
>
> --------------------------------------------------------------------------
> --
> > --------
> > Please do not email me privately with technical issues
>
> --------------------------------------------------------------------------
> --
> > --------
> >
> > Matt Dillon
> > Assistant Moderator: Autodesk Discussion Forums
> >
> > http://www.dccadd.com
> >
> >
> > "Reid M. Addis" wrote in message
> > news:1B2D5CAC7EBD2B2ADE86773A585A3B83@in.WebX.maYIadrTaRb...
> >
> > >Do you REALLY THINK
> > > these people would be capable of using your method??
> >
> >
> >
>
>
Message 15 of 19
Anonymous
in reply to: Anonymous

I've posted a file in Customer Files. If you want to go through the process
that I described and see if it is too difficult for your users, download it
and unzip the two drawing files it contains.

The "2D Tag.dwg" is a custom content file that is a simple 2D block with
attributes. Put it somewhere in your content folder for ADT. The other
drawing is the example drawing that you will be using to try my method out.
It contains a very basic custom door schedule, a custom property set
definition that is attached to two custom door styles, and a modified
object-based door property set definition that only includes the door
number. It took me all of 10 minutes to set this up. It is NOT difficult, if
you understand door styles, schedules, and property sets.

1) Open the example drawing. There are a few doors already placed. You may
want to review the door styles in the drawing and note that I have attached
a property set definition to the styles, that includes a default value for
the "Remarks" field (the default value is different for each style).

2) Using the Design Center, use the STOCK ADT door tags to tag the doors. It
should attach the Door object property definition set and number each door.
Save the drawing.

3) Start a new drawing and go to paper space.

4) Load and set current the "AIA Plantypes" layer key style from the base
drawing (this step would normally be skipped, as you would already have your
layer key style customized - all I did was set the layer key for the ADT tag
to a no-plot status). Also copy the "Door Schedule" style from the base
drawing into your current drawing. (Again, this is something that you would
not normally have to do, as it would already be present).

5) XREF Attach the base drawing in a viewport. You should see the door tags,
but if you do a plot preview, they should not show up.

6) Move to paper space and use ADC to insert the 2D Tag file the same way
you would insert any other ADT symbol. It will come in on a predefined layer
key. For this example, I was sloppy and just stuck it on the DOOR layer key,
but I would create a new annotation key for it - it simply needs to be on a
different layer than the tags that are in the base drawing). Use the tags in
the base drawing to provide you with the correct number for the door number
attribute in the 2D block.

7) Create another viewport and generate your door schedule.

That's pretty much it. Again, you would not have to go through the process
of loading the layer key style, copying the door schedule style, etc.,
because it would be part of a standardized system.

The limitations to this are as follows:
1) You ARE using a non-linked 2D tag to workaround the issue of being able
to tag in paper space and not wanting to annotate the base drawing.
2) You still have to put the schedule in a viewport. Nothing I can think of
to fix that, except, as Reid said, put the model in paper space. I wouldn't.

The benefits are this:
1) You don't annotate your base drawing.
2) You can place your tags in paper space and maintain the model in model
space.
3) Your doors already have all properties except for the door number
pre-attached and pre-assigned as part of the style definition. The user
doesn't have to provide any info at all. It's all part of the style. This
part can be modified - you may wish to leave some values unassigned. In that
scenario, if it was a property whose value would vary among doors of the
same style, I would make it a part of the object-based property set that is
attached when you tag the doors with the stock ADT door tag.

If the above is still too much for your users, then hopefully someone else
can come up with a better solution. Otherwise I see you having two options:
1) Don't use the ADT schedules and tags, but I'm having a hard time
visualizing a system that is easier once it is set up.
2) Change your standard to allow for the annotation to be in the base
drawing, and in model space, which is certainly not what I'm recommending.

--
----------------------------------------------------------------------------
--------
Please do not email me privately with technical issues
----------------------------------------------------------------------------
--------

Matt Dillon
Assistant Moderator: Autodesk Discussion Forums

http://www.dccadd.com


"
Message 16 of 19
Anonymous
in reply to: Anonymous

Beware the dark side.


style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">

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">
Matt,
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?

Message 17 of 19
Anonymous
in reply to: Anonymous

Rob, we are having fun!
For those not wanting to try Matt's solution from scratch, I did it and
placed a copy of my final file in the CF-NG under "ADT3.3 Custom Schedule
Workaround finished". I did what Matt explained above, with the addition of
xrefing the base plan twice: once in modelspace to get the plot scale, etc,
correct; another copy scaled down to 0.0125 original size in paperspace,
placed on the defpoints layer so it won't plot. By placing a second copy in
paperspace, you are able to easily generate your schedule there. Since it's
the same xref, it will update when the base drawing changes.

As Matt says, this is actually MUCH easier in practice than it sounds. I
also apologize for "maligning" all of us smart users out there, even the
ones who throw away plotter parts . I bet anyone could do this.

Is it ideal. No. However, this is one of those situations where after
hitting your head against the wall 3 times, it's time to step back and final
an alternate solution. Matt's is perfectly acceptable.

Regards
------------
Reid M. Addis
Addis Computer Consultants
1-800-841-4418
http://www.addiscomputer.com
raddis@addiscomputer.com
"Matt Dillon" wrote in message
news:4F355B0C52356064FF668CB0E2EF495A@in.WebX.maYIadrTaRb...
> I've posted a file in Customer Files. If you want to go through the
process
> that I described and see if it is too difficult for your users, download
it
> and unzip the two drawing files it contains.
>
> The "2D Tag.dwg" is a custom content file that is a simple 2D block with
> attributes. Put it somewhere in your content folder for ADT. The other
> drawing is the example drawing that you will be using to try my method
out.
> It contains a very basic custom door schedule, a custom property set
> definition that is attached to two custom door styles, and a modified
> object-based door property set definition that only includes the door
> number. It took me all of 10 minutes to set this up. It is NOT difficult,
if
> you understand door styles, schedules, and property sets.
>
> 1) Open the example drawing. There are a few doors already placed. You may
> want to review the door styles in the drawing and note that I have
attached
> a property set definition to the styles, that includes a default value for
> the "Remarks" field (the default value is different for each style).
>
> 2) Using the Design Center, use the STOCK ADT door tags to tag the doors.
It
> should attach the Door object property definition set and number each
door.
> Save the drawing.
>
> 3) Start a new drawing and go to paper space.
>
> 4) Load and set current the "AIA Plantypes" layer key style from the base
> drawing (this step would normally be skipped, as you would already have
your
> layer key style customized - all I did was set the layer key for the ADT
tag
> to a no-plot status). Also copy the "Door Schedule" style from the base
> drawing into your current drawing. (Again, this is something that you
would
> not normally have to do, as it would already be present).
>
> 5) XREF Attach the base drawing in a viewport. You should see the door
tags,
> but if you do a plot preview, they should not show up.
>
> 6) Move to paper space and use ADC to insert the 2D Tag file the same way
> you would insert any other ADT symbol. It will come in on a predefined
layer
> key. For this example, I was sloppy and just stuck it on the DOOR layer
key,
> but I would create a new annotation key for it - it simply needs to be on
a
> different layer than the tags that are in the base drawing). Use the tags
in
> the base drawing to provide you with the correct number for the door
number
> attribute in the 2D block.
>
> 7) Create another viewport and generate your door schedule.
>
> That's pretty much it. Again, you would not have to go through the process
> of loading the layer key style, copying the door schedule style, etc.,
> because it would be part of a standardized system.
>
> The limitations to this are as follows:
> 1) You ARE using a non-linked 2D tag to workaround the issue of being able
> to tag in paper space and not wanting to annotate the base drawing.
> 2) You still have to put the schedule in a viewport. Nothing I can think
of
> to fix that, except, as Reid said, put the model in paper space. I
wouldn't.
>
> The benefits are this:
> 1) You don't annotate your base drawing.
> 2) You can place your tags in paper space and maintain the model in model
> space.
> 3) Your doors already have all properties except for the door number
> pre-attached and pre-assigned as part of the style definition. The user
> doesn't have to provide any info at all. It's all part of the style. This
> part can be modified - you may wish to leave some values unassigned. In
that
> scenario, if it was a property whose value would vary among doors of the
> same style, I would make it a part of the object-based property set that
is
> attached when you tag the doors with the stock ADT door tag.
>
> If the above is still too much for your users, then hopefully someone else
> can come up with a better solution. Otherwise I see you having two
options:
> 1) Don't use the ADT schedules and tags, but I'm having a hard time
> visualizing a system that is easier once it is set up.
> 2) Change your standard to allow for the annotation to be in the base
> drawing, and in model space, which is certainly not what I'm recommending.
>
> --
> --------------------------------------------------------------------------
--
> --------
> Please do not email me privately with technical issues
> --------------------------------------------------------------------------
--
> --------
>
> Matt Dillon
> Assistant Moderator: Autodesk Discussion Forums
>
> http://www.dccadd.com
>
>
> "
>
>
Message 18 of 19
Anonymous
in reply to: Anonymous

I actually tried Matts concept and found it solved some issues I had with
the schedules in Model space.

THANKS Matt.

Just need to remember that I have a plan in paperspace associated to my
schedule.

I am looking forward to the day when ADT will access Schedule Data from DBX.
No opeing drawings and waiting for info.

If DBX is the future of ADT schedules then please remember that all other
products (ie..MS) allow for background quering so you don't have to wait for
the database to be updated to work. So I can work while all information is
updated.

Pleaaaaaaaaaaaaaaaaaaaaaaaaaaaaaase.

--
-------------------------------------------------------------------------
Rob Starz
Plogv 3.0 & 2000 (plot logging) for r14 & 2000
***Enhancement Tools for Arch. Desktop *****
!!!! DormerX out in Sept !!!!
http://www.stardsign.com/main.htm
"Reid M. Addis" wrote in message
news:DE6803E3EBF1F5509E03F1E65F92C6BB@in.WebX.maYIadrTaRb...
> Rob, we are having fun!
> For those not wanting to try Matt's solution from scratch, I did it and
> placed a copy of my final file in the CF-NG under "ADT3.3 Custom Schedule
> Workaround finished". I did what Matt explained above, with the addition
of
> xrefing the base plan twice: once in modelspace to get the plot scale,
etc,
> correct; another copy scaled down to 0.0125 original size in paperspace,
> placed on the defpoints layer so it won't plot. By placing a second copy
in
> paperspace, you are able to easily generate your schedule there. Since
it's
> the same xref, it will update when the base drawing changes.
>
> As Matt says, this is actually MUCH easier in practice than it sounds. I
> also apologize for "maligning" all of us smart users out there, even the
> ones who throw away plotter parts . I bet anyone could do this.
>
> Is it ideal. No. However, this is one of those situations where after
> hitting your head against the wall 3 times, it's time to step back and
final
> an alternate solution. Matt's is perfectly acceptable.
>
> Regards
> ------------
> Reid M. Addis
> Addis Computer Consultants
> 1-800-841-4418
> http://www.addiscomputer.com
> raddis@addiscomputer.com
> "Matt Dillon" wrote in message
> news:4F355B0C52356064FF668CB0E2EF495A@in.WebX.maYIadrTaRb...
> > I've posted a file in Customer Files. If you want to go through the
> process
> > that I described and see if it is too difficult for your users, download
> it
> > and unzip the two drawing files it contains.
> >
> > The "2D Tag.dwg" is a custom content file that is a simple 2D block with
> > attributes. Put it somewhere in your content folder for ADT. The other
> > drawing is the example drawing that you will be using to try my method
> out.
> > It contains a very basic custom door schedule, a custom property set
> > definition that is attached to two custom door styles, and a modified
> > object-based door property set definition that only includes the door
> > number. It took me all of 10 minutes to set this up. It is NOT
difficult,
> if
> > you understand door styles, schedules, and property sets.
> >
> > 1) Open the example drawing. There are a few doors already placed. You
may
> > want to review the door styles in the drawing and note that I have
> attached
> > a property set definition to the styles, that includes a default value
for
> > the "Remarks" field (the default value is different for each style).
> >
> > 2) Using the Design Center, use the STOCK ADT door tags to tag the
doors.
> It
> > should attach the Door object property definition set and number each
> door.
> > Save the drawing.
> >
> > 3) Start a new drawing and go to paper space.
> >
> > 4) Load and set current the "AIA Plantypes" layer key style from the
base
> > drawing (this step would normally be skipped, as you would already have
> your
> > layer key style customized - all I did was set the layer key for the ADT
> tag
> > to a no-plot status). Also copy the "Door Schedule" style from the base
> > drawing into your current drawing. (Again, this is something that you
> would
> > not normally have to do, as it would already be present).
> >
> > 5) XREF Attach the base drawing in a viewport. You should see the door
> tags,
> > but if you do a plot preview, they should not show up.
> >
> > 6) Move to paper space and use ADC to insert the 2D Tag file the same
way
> > you would insert any other ADT symbol. It will come in on a predefined
> layer
> > key. For this example, I was sloppy and just stuck it on the DOOR layer
> key,
> > but I would create a new annotation key for it - it simply needs to be
on
> a
> > different layer than the tags that are in the base drawing). Use the
tags
> in
> > the base drawing to provide you with the correct number for the door
> number
> > attribute in the 2D block.
> >
> > 7) Create another viewport and generate your door schedule.
> >
> > That's pretty much it. Again, you would not have to go through the
process
> > of loading the layer key style, copying the door schedule style, etc.,
> > because it would be part of a standardized system.
> >
> > The limitations to this are as follows:
> > 1) You ARE using a non-linked 2D tag to workaround the issue of being
able
> > to tag in paper space and not wanting to annotate the base drawing.
> > 2) You still have to put the schedule in a viewport. Nothing I can think
> of
> > to fix that, except, as Reid said, put the model in paper space. I
> wouldn't.
> >
> > The benefits are this:
> > 1) You don't annotate your base drawing.
> > 2) You can place your tags in paper space and maintain the model in
model
> > space.
> > 3) Your doors already have all properties except for the door number
> > pre-attached and pre-assigned as part of the style definition. The user
> > doesn't have to provide any info at all. It's all part of the style.
This
> > part can be modified - you may wish to leave some values unassigned. In
> that
> > scenario, if it was a property whose value would vary among doors of the

> > same style, I would make it a part of the object-based property set that
> is
> > attached when you tag the doors with the stock ADT door tag.
> >
> > If the above is still too much for your users, then hopefully someone
else
> > can come up with a better solution. Otherwise I see you having two
> options:
> > 1) Don't use the ADT schedules and tags, but I'm having a hard time
> > visualizing a system that is easier once it is set up.
> > 2) Change your standard to allow for the annotation to be in the base
> > drawing, and in model space, which is certainly not what I'm
recommending.
> >
> > --
>
> --------------------------------------------------------------------------
> --
> > --------
> > Please do not email me privately with technical issues
>
> --------------------------------------------------------------------------
> --
> > --------
> >
> > Matt Dillon
> > Assistant Moderator: Autodesk Discussion Forums
> >
> > http://www.dccadd.com
> >
> >
> > "
> >
> >
>
>
Message 19 of 19
Anonymous
in reply to: Anonymous

chiming in a little late but here is something from the Peter "VBA"
Funk.

Home Work 6.. if you need more info, grab it from my site
www.cadbazaar.com click on VBA Homework.



Here's a tricky one... Attach a tag to a door in an Xref.

The routine will dig into a Xref to get the property infomation attached
to
a door, and then update any attributes in the tag block that have the
"correct" format.

Extra credit:

Maintain the link.

Extra, Extra credit:

Detect un tagged doors

Have fun!

Michael,

Here is what we can do:

1. Xref a drawing with doors that have property sets attached. The
property
information MUST be attached to the door before the xref.
2. Xref the drawing.
3. Insert a bunch of tag blocks. I'm using the block that is inside of
the
Xref. I need a block with attributes for this to work. This could be
part of
the routine.
4. Link the door to the tag
5. Update the attributes in the tag to match the property set
information on
the door.
6. Extra credit, place Xdata on the tag block so the xref drawing could
be
updated.

What we can't do:
1. Use a xref as a "template" for a number of doors. For example, if you
make a drawing of a condo, and then use that drawing in an xref as a
basis
for a whole building, then when you tag the doors, they will all have
the
same number. This is because the tag just looks at the door for the
information, and not at the tag (as did S8).

Let me know how that sounds.

Peter Funk
I'm glad to here that. I'll finish up the homework this evening and post
it.
The only tricky part that I ran into is how to select the door inside of
the
xref. The way that I worked around the problem was to use (nentselp) and
pass in a point. That give me the objectId of the door, and the Xref,
and
then I used the XRefDatabase property of the xref block to get the
object
from the handle. From there, I just looked at the property set and the
block's attributes.

This solution would work with any of the property sets, it really
doesn't
care what type of object it is, it just syncs up attributes with
property
set information.

Cheers,

I've almost got my code finished, but I'm not happy with the error
handling
yet. The nentselp is a major hack, but it works. What you have to do is
send
the full command to the command line. You can't make picks inside of the
lisp call. I first made a VBA selection, saving the object they picked
(the
xref) for later use, and then sent the point where the xref was selected
off
to nentselp.

I'll try to post what I have this week, but I'm off to VA for a couple
of
days tomorrow evening.

Keep at it,
Autodesk, Inc.


bruceclement wrote:
>
> Tell 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.

--

-------------------
Nauman M
CAD Bazaar
*********NEW*********
Add AEC Objects to the Layers(lkey) you want, not the Layers ADT Wants!!
Add a Wall directly on the DEMO Layerkey, instead of switching it later.
Download the eval at http://www.cadbazaar.com
*********NEW*********
Need to easily Navigate to your Custom Content Folders?
Need Autolayering for Dimensions without going through Design Center?
Download the ADT Tools for ADT 2 & 3 at
http://www.cadbazaar.com

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report