Customized menus.

I wouldn't load just 1 menu, I would load and always have loaded Autocad's
base menu that does not and cannot be changed (via permissions setup).

Then I would load partial menus for the users to get what they want/need
extra.

We have 6 partial menus loaded.
--The 3 that come with AutoCAD Mechanical.
--The Express Tools menu
--Our company standard menu
--The user's "personal" menu

You can set it up so that all of their toolbar modifications happen in the
only menu they can write to, the "personal" menu. If they try changing the
toolbars in any other menu they will get an error becuase they cannot write
to those menus. All of our menus are located on the network in read-only
directories except for the "personal" menu (in you case you'd be using a
"username" menu).

--
Kevin Nehls

menu that is already loaded, enabling the user to start modifying that?

 

Thanks,
I probably wouldn't have thought of a "read only" support directory. Any problems with other support files being in that directory or should I put the standard menu files in a directory (read only) all their own?

Bill

 

I have acad's menus in a separate directory along with the few other acad
files we have customized, acad.pgp, acaddoc.lsp and acad.lsp, etc. So that
I can easily track and update those changes ( I know I'm going against some
of my preaching, but for some files it just has to be done, but NEVER for
the menus <g>).

For our company standard stuff they are different directory just as our
standard blocks are in a separate directory structure. Everything that is
"standard" and located on the network for use (since our "personal" menus
are located locally) is read-only to everyone but me and the network admins.
If something gets screwed up, it's my fault, the network admins won't even
touch the CAD stuff. If they see something on someone's PC that even looks
remotely like a CAD related thing they ask me about it......

--
Kevin Nehls

problems with other support files being in that directory or should I put
the standard menu files in a directory (read only) all their own?

 

Further, and just to make sure you get confused, Autodesk added one more MNU
/ MNS / MNC "feature!

Start with a MNU file ... (note you can keep comments in an MNU behind '///)

Load the MNU...
ACAD creates
MNS (stripping comments) and
MNC (compiled for active use)

Also- the MNR stores toolbar settings and code.

Now - for pandemonium (if you wish).
Delete the MNU and MNS files. (in all folders in your search path)
Open ACAD... be sure the MNC is loaded
Close ACAD.

Open the MNC's folder. See the MNS file? Where's it from?

 

Minor change proposed:

(setq local_Menuname (getvar "loginname")
(command "menuload" local_menuname)
)

Now offer each user the option to create & maintain their own ... at their
own risk.