James,
OK, you're completely missing the point. I AM USING LAYERS. You set
the shrinkwrap on say "A-Wall" and the hatch on say "A-Wall-Patt".
You're doing this in the display properties correct? When you click on
the component and choose it's layer, where does the layer come from? It
comes from the current drawing, right? The layer AND IT'S PROPERTIES
(color, linetype, etc) are now part of that style.
So you're done with setting up the styles you want, and you save this
drawing as your company standard styles file. Open a new drawing,
without any layers in it. Now bring in one of the styles from your
standard drawing by copying it in Style Manager. You haven't added any
of the new objects yet. Close Style Manager and go to the Layer dialog.
See the new layers there? The properties you see (color, linetype,
etc) came from the style, and not from any layer key, anywhere.
So, given this scenario, wouldn't it make sense to select a KEY instead
of a LAYER when defining the properties of a style? So the shrinkwrap
would go on the layer created by the key "WALL" and the wall hatch would
go on the layer created by the key "WALLPATT". No layers and no layer
properties are defined in the style, they're all defined in the Layer
Key file you so painstakingly edited. It's the same key file used in
every other situation in ADT to create a layer, EXCEPT THIS ONE.
-Danny
James Buzbee wrote:
>>These are Wish List items. I want Autodesk to make my life easier,
>>don't you?
>>
> Well, sure.
>
> #1. Here's a common scenario: Speaking specifically of walls; I have plans
> at different scales that reference the same xref "X_Base.dwg". At 1/16" =
> 1'-0" all I want to see is the shrink wrap. At 1/8" = 1'-0" perhaps the
> wall hatch. At 1/4" = 1'-0" I show everything. Right now all that is
> easily controllable by layers. I know - you can do the same with the
> display - but my argument hinges on the notion of using only one display
> device. So, since not all objects in an architectural drawing will, or can
> be, ADT objects why not use layers?
>
> #4. Yea, that would be nice. I've written a pretty extensive application
> that does just that for all my annotaion objects with respect to layers and
> styles - very powerful. I would love AutoDesk to come up with the same
> thing for ADT objects!
>
> jb
>
>
>
>
>
> "Danny P." wrote in message
> news:3C9B8EBA.8010205@nspam.perkinswill.com...
>
>>James,
>>
>>#1. I'm not saying that layers aren't the "most convenient and powerful
>>method of controlling visibility." What I'm saying is that the layers
>>are defined in the style, and when you import a style, the layers come
>>with it. Instead, you should be able to reference a Key like "WALL" so
>>that the components come in on the layer keyed to WALL, with the
>>properties defined in the KEY not in the STYLE. Why should a style
>>control layer properties?
>>
>>#4. I'm well aware of the ability to import styles via ObjectDBX, in
>>fact we're doing it. However, why would I want to set up a reactor for
>>every object type and every style, load that particular style via
>>ObjectDBX, then make sure the Add command uses the correct style, when a
>>simple macro like ("AecWallAdd" "ST" "MyWall") can bring in the style
>>for me? It's so much easier. A system variable defining a standard
>>style drawing will make it happen.
>>
>>These are Wish List items. I want Autodesk to make my life easier,
>>don't you?
>>
>>-Danny
>>
>>
>>
>>James Buzbee wrote:
>>
>>
>>>Danny, How's Atlanta these days?
>>>
>>>Sorry to disagree with #1 (as you eluded to in #6) - Layers are still
>>>
> the
>
>>>most convienant and powerful method of controlling visibility. Only
>>>
> about
>
>>>65% of my Architectural plans are ADT objects, the rest are dumb lines,
>>>arcs, etc. I have written an app that allows me, or anyone else, to
>>>
> easily
>
>>>set up layer configurations for different type plans and then apply them
>>>
> to
>
>>>the current doc. All my styles are defined "bylayer". I don't even
>>>
> bother
>
>>>with the Object Display thing.
>>>
>>>As for #4 - the "standard" file mentioned above also has all my standard
>>>
> ADT
>
>>>styles. You can use ObjectDBX to import the styles as needed.
>>>
>>>#5 - YES, multiple line room tags!
>>>
>>>
>>>
>>>"Danny P." wrote in message
>>>news:3C9A85CC.1040809@nspam.perkinswill.com...
>>>
>>>
>>>>I think everyone would agree that the development team can benefit from
>>>>this kind of feedback and I haven't seen a thread like this in sometime,
>>>> so please post some customizaiton wish list items if you have any.
>>>>
>>>>For dxf related items, reply to Peter's post from a couple days ago.
>>>>Also, please see "ActiveX Wish List" on 7/18/01 started by Peter.
>>>>
>>>>I'll start:
>>>>
>>>>1. Object display properties should really reference Layer Keys and not
>>>>layers. You've got a key system, use it. The fact that a layer is
>>>>defined in a style with certain properties, and is added to the drawing
>>>>when the style is added, is counter to the theory of using keys in the
>>>>first place.
>>>>
>>>>2. Allow objects to be placed on different Layer Key layers. Allow us
>>>>to add a wall on a layer key called "MYWALL" instead of always on
>>>>
> "WALL".
>
>>>>3. Purge and reimport the current Layer Key Style when opening a
>>>>drawing so it's always current. You've heard this before.
>>>>
>>>>4. Have a system setting for a standard style file, kind of like
>>>>acad.pat. If I have a macro something like ("AECWALLADD" "ST"
>>>>"MyStyle"), and "MyStyle" doesn't exist, go to the standard style file
>>>>and automatically import it. Most of us probably have a standard style
>>>>file, and our styles are not in the template (as Adesk has suggested
>>>>too), so this functionality would make sense.
>>>>
>>>>5. Not really a customization item, but I'll request it anyway:
>>>>Automatic concatenation in a schedule table. RoomName1 and RoomName2
>>>>combined in the schedule as RoomName. Or multi-line attribute defs.
>>>>
>>>>6. Event reactor for display configuration change. Although some of
>>>>the visibility items are handled by the display system, we'll always
>>>>have layers, and I'd like to freeze/thaw some of them when that happens.
>>>>
>>>>7. Rob covered most of my other requests with his DXF hack list.
>>>>
>>>>Thanks,
>>>>Danny Polkinhorn
>>>>Perkins & Will
>>>>Atlanta
>>>>
>>>>
>>>>
>>>
>
>