How do you save & restore parts of the default.cui?

Now that I have the Context Menu's "Entity Snap" to look like my "pop0" menu does in AutoCAD, how do I save those changes so I can bring them back should the default.cui get updated?I don't see any method to save just part of the menu.It also looks like any partial menu elements imported that have names matching existing names is lost (can't overwrite with new info.)I'd rather not repeat all the edits each time a new default.cui menu us released.As an alternate can you re-direct an exiting context menu in the default to a partial menu installed later?

Comments

  • Also the import and on the fly conversion of .icm or .mnu files does not seem to be tiptop.While we are at it If one moves around some icontoolbars and start editing a menu, all the icons jump right back to default. Really annoying. Has anyone managed to rearrange the menu layout graphically or does one have to handtype .cui files ?Patrik

  • I made an .mnu file out of my last .icm. Tedious, but I won't get caught not knowing where my customisations are again. Some Acad users still do the same, they probably stuck with .mnu all along.

  • Indeed, there is no method to save a part of the menu. To create an entity snap context menu in a partial menu file, you can either copy and edit parts of default.cui, or use the customize dialog to create a new partial cui file, and create a new entity snap context menu in this partial menu group. When the entity snap context menu is ready in the partial menu group, delete the one in the BRICSCAD menu group.When default.cui gets updated, reload the partial cui file and delete BRICSCAD's entity snap context menu.

  • Before I install a new version I backup my CUI file and use a File compare utility to highlights the differences between the two files. This suites me well as with several mouseclicks I move the parts that I included into the newer CUI file.I use http://www.grigsoft.com/wincmp3.htmA free program is http://winmerge.org/

  • I have not tried this yet but I used to do this in Ver up to 7.Do your fix graphically.Dump all std menusexportreset defaultimport the file with append.Is this still possible ?The fact that the .cui file handles both toolbars and menus is slightly messy I think.Patrik

  • Well .... I tried the delete everything but the section I wanted to save, but a large number of the "Available Tools" will not delete using the Customize Dialog Box. Even after you delete all of the menus & tool bars these "Tools" are still referenced and thus will not delete.I ended up repeating all of my edits in the Customize Dialog Box (took way too long) under a new menu. Why is there no "drag-n-drop" ?(Being able to change menu order by dragging would also be nice.)After "Reverting to defaults", deleting the "Entity Snap" menu, and loading the partial menu I just created, the process worked. I have no idea why the program linked to my new menu. Does it link to Title, ID, or Alias?Editing the old .mnu files were much easier than these new .cui files. In the .mnu file a command was one line, in the .cui file a command could more than a page of text.The next thing I need to try is making the menu common to all the workstations.

  • I tried the latest release, v8.1.14 .....Looks like we have lost ground in the custom Context Menu for my middle mouse button concept.My edits for the "Entity Snap" context menu were lost in the upgrade (that could be my error) but process I used before (delete default menu and re-entering the custom version as a parital .cui) failed.How do I get the program to use my custom "Entity Snap" menu?

  • Indeed, V8.1.14 doesn't find the custom Entity Snap menu in a partial menugroup anymore. We will fix this with priority.

  • The custom Entity Snap menu problem is fixed (rev.10196)

  • (The fix mentioned in the previous post will become available in the next release)

  • Another approach to keeping your menu customization when changing to a new version of Bricscad:Make your custom CUI file the "main" CUI file, and attach "default.cui" to it as a "partial" CUI file. That's all.Then you don't have to do anything when you update. The new "default.cui" overwrites the old one, and replaces it as the "partial" CUI attached to your custom CUI file. It automatically updates, just like an xref drawing file that you edit or replace with another file of the same name.Another advantage of this method is that if you've customized the Context menus, your versions are used instead of the default ones, since yours are in the "main" file. You don't have to delete the default context menus, or make any change at all to the new default menu file when you update.I just installed version 9 for the first time, and didn't have to do anything about menus except answer yes to the question about copying support files from the older version. The first time I started it up, my custom menus were there along with the new default menus, and my customized context menus worked, and all the toolbars were set on or off just as I had them in version 8.

  • Cool! I like that...

  • Hi Anthony Apostolaros how do you set up your custom cui file as the "main" cui file?

  • A "partial CUI file" is analogous to an Xref'd DWG file. Any CUI file can be attached as a "partial" to any other CUI file, just as any DWG file can be attached as an Xref to any other DWG file.You decide which CUI file is the main, and open it with the "Load Main" command. Then use the "Load Partial" command to attach another CUI file to it.But a Partial is unlike an Xref in these two ways:-- you can edit a partial CUI file while it's loaded as a partial;-- when you save the main file, the partial file is also updated to include any changes you made to it.

  • To choose your main CUI file, click the Browse button on the right hand side of the 'Main Customization File' field on the Customize dialog, then open your main CUI file on the 'Select main CUI file' dialog.

  • I've been using a customized menu as my main CUI, and using each "new" default.cui as an attached partial CUI, just the way Anthony has described. It's worked real well until V10. Using V10, the attached default.cui is overriding my custom context menus even tho it's being used as an attached partial menu.

    Am I the only one? What am I missing?

This discussion has been closed.