How to deploy Enterprise CUIX from ACAD.lsp with working Menus, no profile required

[blkcar]

I've spent the last few days trying to find a simple solution to this problem. I've seen the same problem submitted by multiple people but no fix. Below is how I got it to work, hopefully this might be of help to someone.

1. Create a new workspace in the acad.cuix by duplicating the Drafting & Annotation workspace, rename to suit eg. Workspace 1.

2. Select new workspace then select customise workspace, add new menus from your enterprise cuix. Click done  & apply. (Note: You might need to give new menus a sequential POP# under aliases to ensure the show correctly.)

3. Go to transfer tab, transfer newly created workspace across & supporting lisp files if needed. Save customisations in new file, this will be you new cuix file.

4. In acad.lsp add this line of code, adjust path & filename to suit.

(vla-put-EnterpriseMenuFile *myFiles* (strcat *server* "\\CAD\\Support\\[file name here].cuix"))

Work with acad.lsp in this handout https://www.autodesk.com/autodesk-university/class/Deployments-and-AutoLISP-Strategies-Easy-Installa...

5.  Add this code to specify the name of workspace previously created in cuix.

(setvar "WSCURRENT" "Workspace1")

6. Add this line to make menu bar visible always defaults to "0" otherwise.

(setvar "menubar" 1)

That's it, pretty simple just a matter of getting all the pieces in the right order. Its not perfect as the menubar will turn off when switching to another workspace & back again. Don't know how to fix that in code, in our office no one changes workspace that much so its not a major issue. Also if user creates custom arg for themselves that should fix it.

[JamesMaeding]

I love the idea of workspaces, and actually wrote a tool called Menusback a few versions before adesk introduced them.

To this day, workspaces and the CUI system have critical defects. My users regularly get bit by them.

So the way we play it is:

1) robocopy all needed to users C drive, no tools or menus called from a server, especially for remote people.

2) I create a company standard profile (arg) that sets up the initial condition, with menus and all loaded.

3) for pulldowns, I have Menusback which still works, it uses lisp code for pulldowns.

That tool is free, and part of my stuff you can download. Look up "purgeids" for that link.

It looks like this, and is what the old Menuload command used to have as a second tab:

The right side is vertical but is what the menus will be across the top.

The toolbars and states features do not work now, because adesk "broke" the com menu interface "on accident" once I showed them all this. Magically, workspaces come out a year later. I'm not fooled.

[pbejse]

I prefer the use of deployment package found here in conjunction with a vlx/net  to read the server files for any updates.

Surprisingly easy to use.

[Sea-Haven]

My $0.05 I use CIV3d so there are 2 workspaces that get used all the time, the drafting and the CIV3D, so rather than jumping between them all the time made custom menu and toolbars, the commands inside them are made by pulling all the details from various workspace menus. Just open cui and have notepad custom mnu open, so cut and paste. This covered like 90 % of our daily tasks without changing work spaces.