>> theory that 50% of toolbar buttons are for demos, and many important
>> everyday use buttons are missing.
Yeah, but who am I to tell the user what is and isn't an important
toolbutton? Maybe some users rely on the "?" icon for Help, hehe.
Also, they can always turn on and off standard toolbars. New employees
appreciate it too.
>>Also, I have changed the behavior of
> things like CopyClip to default to ask for a base point.
Yes, this is one of my custom commands. My office has 2 copyclip icons. One
is the standard, which some people still like using, and the other is
slightly modified to include a base point option. Our custom stuff is on a
separate toolbar (and menu) and has a different looking icon.
"Gordon Price" wrote in message
news:670E36BA4F43BC84B13499C07C9EF1A2@in.WebX.maYIadrTaRb...
>
> "F. Gump" wrote in message
> news:CA0FF1725F341E789B66924273FAC9F3@in.WebX.maYIadrTaRb...
> > We do NOT customize the standard ACAD stuff. All of our customizations
go
> in
> > a separate add-in menu. It will carry over to the next release alot
easier
> > this way, and its easy to backup that single menu for safe-keeping.
> I used to not, but a couple of things have come up that suggest it is a
good
> idea. I have cleaned up the menus based on the Woody's Word Annoyances
> theory that 50% of toolbar buttons are for demos, and many important
> everyday use buttons are missing. Also, I have changed the behavior of
> things like CopyClip to default to ask for a base point. Perhaps this can
be
> done with a custom menu partial load and I couldn't figure out how?
>
> > We also use the "autoload" command alot, so that custom commands are
only
> > loaded when the user needs it.
> > I wish Autocad would do that. It would make loading up autocad alot
> faster.
> I agree with you there. Having ADT load everything, when the design phase
> lasts months, then the documentation phase lasts months, is a pain. So
much
> better to just load the tools you need. Ideally I would like to define the
> 'Phase' a project is in, then define what tools are preloaded for each
> phase. When a user opens a file, it ids the project, get's the phase the
> project is in, and preloads a subset of tools appropriate to that phase.
> everything else is demand loaded. In a perfect world 😉
>
> Best,
> Gordon
>
>