View Full Version : 2006 CUI and Mouse Button Menu
de-co1
2006-04-13, 01:24 PM
We have just upgraded to LT2006, but I suspect the process will be the same as full 2006, and I will probably be better served posting this here instead of the LT forum...
In my CUI, I am able to import partial custom menus from previous versions of ACAD. In my case, I have tried to import my customised mouse short cut menu (that pops up when I control+click).
I have managed to bring it in and have created a personalised custom CUI, which I can see and edit. I have also managed to load this up as my workspace. The problem is that everything but my mouse button pop-up works. My custom toolbars have come in OK (and no clouds with ? marks), and work fine, all in the location as before... but not my custom mouse button menu!
In the Customize User Interface, I see the parameters for the standard mouse button refer to the macro $P0=SNAP $p0=* , but I don't know how to redirect it to my Snap Menu, or how to properly integrate my menu without changing the original aclt.cui file.
My searches online haven't produced anything that really helps me.
TIA
de-co1
2006-04-13, 01:42 PM
OK... I have just found the following threads
CUI and Mouse Buttons (http://forums.augi.com/showthread.php?t=23194&highlight=mouse+button+menu)
NEED HELP WITH MOUSE BUTTONS WITH 2006 (http://forums.augi.com/showthread.php?t=23600&highlight=mouse+button+menu)
I will have a look at these and try the suggestions out...
(Edit: OK, this doesn't seem as straight forward / easy as I hoped it would be. Still can't get it to work)
RobertB
2006-04-14, 05:24 AM
Since the first loaded instance of a shortcut menu wins, your only course without editing AcLT.cui is to use your cui file as main, and load AcLT.cui as partial to it. Or, if LT supports enterprise cui files, to load you cui file as the enterprise and leave AcLT.cui as main.
de-co1
2006-04-18, 07:51 AM
Thanks Robert,
There is reference to the Enterprise CUI, but I can't see where I can apply it as suggested in the links I posted above. I will try making my custom CUI the main one, and load LT's CUI as partial, as you suggest.
de-co1
2006-04-18, 10:13 AM
OK... the story so far.
I am able to create an Enterprise CUI. I simply copied the original file out, renamed it, and placed it back in the support folder under MYNAMEApplication DataAutodeskAutoCad LT 2006R11enusupport.
I then set this under my options as the main CUI, so when I open up my CUI, I note that the enterprise.CUI is my main CUI.
I started editing this. I imported my shortcut menu from my ACAD LT 2000 menu file. It comes in OK, and is situated under my SHORTCUT MENUS in the CUI. The list I bring in is all OK, and everything is there.
I rename my custom Shortcut menu to DIR Custom Menu. Under its properties, I change the following...
Name = &DIR Custom Menu - (Don't think the '&' is necessary, but it doesn't seem to make a difference)
Aliases = POP517, DIR (originally had POP517, POP517 as the alias assigned by default, and I changed it to suit the original Object Snap Menu's alias format of POP0, SNAP)
I then went to my Mouse Buttons and noted that the only settings for SHIFT+Right Click, CTRL+Right Click and SHIFT+CTRL+Right Click were Object Snap and Snap Menu as default.
I have tried various formats, but in the end I am sitting with each of the above having only my Custom Menu assigned to Button 2 (seems to default to button 2). I have also placed a blank button as Button two, and made my custom menu button 3, and I have also left the original buttons, and simply adjusted the orders.
With my menu set to a button, the button then has the following properties.
Name = DIR Custom Menu
Macro = $P517=DIR $p517=* - Again, I followed the original Object Snap Menu's format of $P0=SNAP $p0=*
I suppose once I can get it working and know where I go am going wrong, I will be able to appreciate this new format for customising, but right now it's doing my head in with a day and a half lost on trying to figure this out....
:banghead: :banghead: :banghead:
EDIT #1 - I have now started from scratch again with the original CUI file. I have saved it as an enterprise.CUI, and made this the default Main CUI. I have imported my shortcut menu from my previous LT2002 .MNS file. I then created a new command in the Commands List for this Menu. I created new mouse buttons, and then dragged this command onto the new buttons. I deleted ALL the buttons for Object Snap Menu, as well as OSNAP settings. I redefined my macros and aliases as above.
With NO OSNAP settings or Object Snap menu defined in any of my buttons, these still open up, even though I have my new custom menu defined in the macros and aliases.
I have no partial menus loaded, and no additional workspaces. It is all a 'blank canvas' so to speak.
Hi David,
In your custom menu, try $P0=&DIR Custom Menu .POP517 $P0=* as the macro for the button.
(don't forget the period between the menu name and the pop)
Assuming that the custom menu is still named "&DIR Custom Menu" , and POP517 is still the alias of your shortcut menu in &DIR Custom Menu.
BTW, if I remember right from the videos HERE (http://forums.augi.com/showthread.php?t=19301), if a menu is set to the Enterprise Menu, it is read only, and you can't edit it until you change the enterprise menu in options to something else (or ".").
Also, the ampersand (&) tells AutoCAD the the letter following is the mnemonic (letter to press to activate that menu/item if using a keyboard) for that menu, and you probably don't need it.
I still use a tablet, and this drove me up the wall for a while, also.
HTH, let us know if not.
de-co1
2006-04-19, 07:39 AM
:Puffy:
THAT'S SORTED IT!
After reading through quite a bit of info on this, I realised it had something to with my macros, but wasn't able to put two and two together... I had thought that the macro needed to include only the alias and didn't realise it had to include the shortcut menu's name.
Thanks Tim, you've made my day so much better.
:beer:
Your welcome.
I'm glad I could help.
:beer: :beer:
Powered by vBulletin® Version 4.2.5 Copyright © 2025 vBulletin Solutions Inc. All rights reserved.