Managing your CUI

[LElkins]

I am just making a few changes to my office standard CUI, and thought I would find out how you all handle it.

Do you map each machine to read the main CUI from a central location, so everyone has the same cui, or do you load your company custom CUI as a partial?

Any negatives/benefits to each?

Cheers

[Ritch7]

at our place were all the same, theirs only a few cad workstations but to my knowledge the computer user interface's are almost identical if not 100%, just generaly makes it easier dont you agree? does your company do the same?

[NBC]

I load our custom cui as a partial (from a network location) into the main acad.cui
to do this, i have created a basic lsp file which is run on everyones' machine each time they open a drawing.
whatever is shared on the network will be loaded onto each machine.
I keep a backup copy of our custom cui on my local machine, for if i need to tweak anything in it

[LElkins]

Anyone working with the main cui mapped to a central location, so all are singing from the same hymn sheet??

[Hedgehog]

Nope... & I can't imagine I'd ever go down that route... it might be handy to have a few standard routines but I customise mine to hell to suit my methods which are extremely fast & I don't expect others to follow (tho' some here are taking to them). Nothing really to do with company or CAD standards so leave 'em to the individual (until they mess 'em up of course).

/edit... I suppose, also, that the standard main CUI is fine for us in our office to work away from... therefore if it wasn't suited to your line of work I could see a value in having a central or replacement CUI.

[Teeds]

I load our custom cui as a partial (from a network location) into the main acad.cui
to do this, i have created a basic lsp file which is run on everyones' machine each time they open a drawing.
whatever is shared on the network will be loaded onto each machine.
I keep a backup copy of our custom cui on my local machine, for if i need to tweak anything in it

I used to have the system set up this way when I was responsible for the CAD at a large firm and we used DOS as the OS. Since going into business for myself, this has not been an issue. I only have two seats to keep track of and they are mine and my daughters. Frankly, these days, she is more likely to make mods than I am.

I lost a perfectly good MNU file with 15 years of development when AutoCAD made the jump to CUI. Bummer.

My opinion these days would be to keep a copy of the main CUI on the network so you can rebuild a machine if necessary, set up the basics and let the power users have the space they need to explore.

I would identify them and try to keep on top of what they are doing and discovering. Your power users might be coming up with some real gems that could be incorporated into the office standards.

[ML0940]

In my past position, I took advantage of the enterprise cui and happen to favor that method the best.

Where I am now, we have 2 partial company cu files that are on a network share.


On a side note:
Does anyone still edit their mns file and load it back into acad to convert it to a cui or do you just edit the cui?

While I like the cui in theory; I think AutoDesk still has work to do with it. I still prefer the search and replace methods in a text editor over the cui editor