Basic commands missing from my CUI - Conflict or User Error?

[fdebolt]

Out office got 2006 November last year and I spent a couple months creating custom toolbars in 2006 in the new CUI format, converting from our old MNU format on my machine and then installed 2006 on all our machines today with the enterprise CUI. It appears we lost the basic commands such as pull down edit-select all and another example is make current from the layer toolbar. When I load the Enterprise CUI as the standard CUI acad.cui I can get back a few of them, but not all.

Did I cause this or do I need a patch? I am lost and am not sure what to do. This was very unexpected and I see no posts that address this issue. Everybody was excited about 2006 and the company toolbars, now that has died off and people want the custom stuff taken off and their basic commands back. Any suggestions?

[Mike.Perry]

Hi

Please note I have *moved* this thread from the AutoCAD Customization (http://forums.augi.com/forumdisplay.php?f=118) forum to this one as I believe it would be better served here.

Thanks, Mike

Forum Moderator

[Opie]

Out office got 2006 November last year and I spent a couple months creating custom toolbars in 2006 in the new CUI format, converting from our old MNU format on my machine and then installed 2006 on all our machines today with the enterprise CUI. It appears we lost the basic commands such as pull down edit-select all and another example is make current from the layer toolbar. When I load the Enterprise CUI as the standard CUI acad.cui I can get back a few of them, but not all.

Did I cause this or do I need a patch? I am lost and am not sure what to do. This was very unexpected and I see no posts that address this issue. Everybody was excited about 2006 and the company toolbars, now that has died off and people want the custom stuff taken off and their basic commands back. Any suggestions?
Do you load the acad.cui OOTB as a partial menu? Did you customize the acad.cui instead? What is your enterprise CUI set to?

[jpaulsen]

It sounds like the acad.cui has been modified.

I would suggest getting a copy of the original acad.cui and setting that as your enterprise cui. Your custom menus and toolbars should be in a separate cui that is loaded as a partial to the acad.cui.

If you want to allow your users to create their own menus and buttons load the custom.cui as the main.

[fdebolt]

I loaded the custom CUI as NC.CUI and brought it in as the enterprise and left the ACAD as the main CUI.

[Opie]

I loaded the custom CUI as NC.CUI and brought it in as the enterprise and left the ACAD as the main CUI.
Are you using duplicate names that may conflict with the ACAD.CUI names?

[fdebolt]

Duplicate names in commands? Or file structure? I suspect that I am not, since all the commands work on my machine that I created the custom work on before migrating to the other computers.

The error message reads as unknown command. I spot checked some and they are not in the PGP or doc.lsp files.

[jm.pearson105333]

It sounds like you may have customized your CUI incorrectly. I made the same mistake. There are two panes in the CUI command, and anything you move from the left pane is a universal change. If you delete something from the menus/toolbars in the left pane, it's gone from the defaults. You will have to re-insert it from the Command List at the bottom left of the CUI box. Do all of your editing in the right pane.