Author Topic: Menu Incompatibility  (Read 1881 times)

0 Members and 1 Guest are viewing this topic.

hudster

  • Gator
  • Posts: 2848
Menu Incompatibility
« on: March 29, 2005, 11:24:52 AM »
Up till now we were using custom menus shared via a network drive with no problems.

But now we have a 3D specialist contractor on board doing sun path analysis work for us, he is using his own companies version of 2005, but when ever he loads our menus, I have to delete the MNC and MNR files before my version of 2000 will load the menus.

Is there an easy way round this or will I have to keep deleting the files every time I load AutoCAD.
Revit BDS 2017, 2016, 2015, 2014, AutoCAD 2017, 2016, Navisworks 2017, 2016, BIM360 Glue

Mark

  • Custom Title
  • Seagull
  • Posts: 28762
Menu Incompatibility
« Reply #1 on: March 29, 2005, 12:48:44 PM »
The only thing I can think of is let him have a copy of the menus all to himself.
TheSwamp.org  (serving the CAD community since 2003)

pmvliet

  • Guest
Menu Incompatibility
« Reply #2 on: March 29, 2005, 12:57:50 PM »
2k4 and from what you are saying 2k5 menu's do not play well with others like 2k2  :(
what I had to do was make my menu's specific for the platform.
So I just added a version like addon2k2.mnu...

Pieter

hudster

  • Gator
  • Posts: 2848
Menu Incompatibility
« Reply #3 on: March 29, 2005, 02:15:31 PM »
Quote from: pmvliet
2k4 and from what you are saying 2k5 menu's do not play well with others like 2k2  :(


thats what I was afraid of.

I'm constantly changing/updating these menus as required by new layers, blocks etc, and It would be easier if we all could se the same versions.

Looks like i'll have to think of something else.
Revit BDS 2017, 2016, 2015, 2014, AutoCAD 2017, 2016, Navisworks 2017, 2016, BIM360 Glue

MikePerry

  • Guest
Menu Incompatibility
« Reply #4 on: March 29, 2005, 05:35:32 PM »
Hi

Below snippet comes from an old CADManagers Guild post from Richard Binning -

<snip>
Having them both on the same machine poses no problem unless you are pointing both version to the same custom menu.
Remember that although you may have them in separate folders, if autocad finds the menu first from the wrong location , then it might load that.

Make sure you don't hve this custom menu in the search path of both versions.

If you really want to use the same menu for both versions, then you can recompile the menu on the fly!

Try this code:

1.) save the following code to a file named acaddoc.lsp so that it loads prior to the menu being loaded.

2.) add the folder containing your custom menu and this acaddoc.lsp to your support file search path and push it up to the top of the pile.

3.) modify the code below replacing the word "Personal" with the name of your custom menu. (Note: personal is both the file name and the menugroup name.

;code below

Code: [Select]
(vl-load-com)
(if (findfile "Personal.mnr")
  (vl-file-delete (findfile "personal.mnr"))
)
(if (findfile "Personal.mnt")
  (vl-file-delete (findfile "personal.mnt"))
)
(if (findfile "Personal.mnc")
  (vl-file-delete (findfile "personal.mnc"))
)
;set the flag
(setq flag1 T)
;check if the menu is already loaded
(setq loaded (menugroup "PERSONAL"))
;if it is not loaded
(if (= loaded nil)
;do the following
  (progn
;find the menu file
(setq temp (findfile "PERSONAL.MNS"))
;if you find the menu
(if temp
;do the following
 (progn
;switch off dialogues
 (setvar "FILEDIA" 0)
;load the menu
 (command "menuload" "PERSONAL")
;switch on dialogues
 (setvar "FILEDIA" 1)
;install the pulldown
 (menucmd "P21=+PERSONAL.POP1")
;inform the user
 (prompt "\nLoading Users Personal Menu....\n")
 ) ;progn
;menu not found, so do the following
 (progn
;inform the user
 (alert "Cannot Locate THC Menu. \nRe-Run Install.")
;clear the flag
 (setq flag1 nil)
 ) ;progn
) ;if
  ) ;progn
  (progn
;Menu previously loaded so lets unload it now
;unload the menu
(command "menuunload" "PERSONAL")
;find the menu file
(setq temp (findfile "PERSONAL.MNS"))
;if you find the menu
(if temp
;do the following
 (progn
;switch off dialogues
 (setvar "FILEDIA" 0)
;load the menu
 (command "menuload" "PERSONAL")
;switch on dialogues
 (setvar "FILEDIA" 1)
;install the pulldown
 (menucmd "P21=+PERSONAL.POP1")
;inform the user
 (prompt "\nLoading Users Personal
Menu....\n")
 ) ;progn
;menu not found, so do the following
 (progn
;inform the user
 (alert
   "Cannot Locate Users Personal Menu.
\nRe-Run Install."
 )
;clear the flag
 (setq flag1 nil)
 ) ;progn
) ;if found
  ) ;progn
) ;if loaded

Note: Bob Bell is reporting some crashing problems with just recompiling the menu... so I added the menu load/unload sequence. I haven't had any problems since.

Running ADT33 and ADT2004 with a common custom menu.

Thanks,

Richard Binning

CADD Coordinator
</snip>

Have a good one, Mike

hudster

  • Gator
  • Posts: 2848
Menu Incompatibility
« Reply #5 on: March 30, 2005, 10:10:44 AM »
brilliant, this works superbly.
Revit BDS 2017, 2016, 2015, 2014, AutoCAD 2017, 2016, Navisworks 2017, 2016, BIM360 Glue

pmvliet

  • Guest
Menu Incompatibility
« Reply #6 on: April 01, 2005, 10:41:12 AM »
could someone with access to 2006 see if it messes with a 2004 or 2005. I read all the stuff about the new/updated menu structure.

2004 & 5 can share the same menu and I need to know about 6.

Thanks,

Pieter