#Saving Xref Settings
9 messages in this thread
I second and thrid the request to fix the layer control in XRefs. Please
note Brad, Malcom and Dufs Compuserve number so we can all pass the message
along. I use XRefs a lot and love the concept. Unfortunately the xref'd
drawings sets the stage with the layer control which is contrary to what we
need in a parent / child relationship. I've conjured up numerous
workarounds, none of which are too good. I think the main problem for lack
of user response is many people haven't upgraded to R11 and or haven't seen
the powerful benefit of this relational approach to drawing control.
John Long
John – Thanks for your comments. I've moved from Tech into Training, so
you might want to ask someone to forward your concerns to John Lynch, the
Release 12 project manager.
Brad,
Was the move a reward, a reprieve or a request? Just being nosey.
Dennis
Dennis,
It was a Godsend to us in the Training department! For Brad, a respite,
I'm sure <grin>.
Dieter
Dennis – Working on Release 12 was one of the great experiences of my life.
There were two rewards: helping to shape the product in some small ways
that I think our customers will find useful (if the purpose of a business
is to create and keep a customer, then one way to help reach that end is to
make great product), and working with people like Bill Adkison, K.C. Jones,
Mauri Laitinen, Scott Heath, Duff Kurland, Patti Harris, Carolyn Hedrich,
Jim Gloystein, Jan Yoder, Ian Kitching, Monte Meals, Greg Lutz, Bob Elman,
Dan Drake, Bill Howison, Yuan Yu, Greg Milliken, Creighton Hoke, Kern
Sibbald, Pamela Nice, Trevor Fougere, Marc Ramsey and many, many others was
both personally and professionally rewarding. These are wonderful people,
and I still find it hard to believe that I was given the opportunity to
work with them.
Like the AutoCAD development groups, the Training department is also
composed of wonderful people, and I'm very pleased to be a part of it
again.
But the dealers should be warned. Zehring's back in town, and they'd
better know their basic AutoLISP before R12 training: the salespeople from
the standpoint of what it can do for their customers, and the bits and
bytes for the technical folks.
Gotta lot of…interesting…stuff to cover.
Gee, Brad-
It sounds like you are just the person to help lead the training program in
the directions necessary to make R12 blow everyone's socks off; what with
your presumably intimate knowledge of the features of R12, knowledge of the
process of the development of each feature, of what/how/when the feature was
designed to be used, and of course all of the excitement that you show
whenever you talk about R12 here… Who could be better? Congrat's to
Autodesk for another smart move!
Gee, I guess I won't be able to bugg you about that display list extents
issue anymore (I'll bet you're glad, right?) <g>. I think I'll aim that one
at Lynch, now.
Peter – Well, thank you. The Training group has been working on Release 12
for months, and they've already covered just about everything. My
contributions this time around will focus on the areas of AutoCAD's user
programming interfaces.
If you haven't seen the new API for AME Release 2, take a look at it. It's
fantastic, and it can be driven through either ADS or – get this –
AutoLISP. Just about anyone with a basic knowledge of AutoLISP can create
parametric routines for AME R2. It's very, very cool.
Brad – so *that's* where Jan Yoder went! I haven't noticed his smiling ASCII
around here lately.
Glad you had a good time, glad you're back!
Dave
Dave – <Smiling> Jan worked for some months in the Core group, making
contributions to R12 a variety of areas. He left Autodesk a few months ago
to work at a start-up firm in Mill Valley named Stylos. You might have
seen an article or two about them in PC Week. They're developing pen-based
mark-up applications for AutoCAD, among other things. It was great to have
Jan in Core, and we wish him all the best at Stylos.