James, the mouse buttons work fine in the outlined scenario, in vanilla or
ABS. There is either something odd in the civil stuff, or there is something
I've forgotten to tell you.
BTW Matt, I usually advocate starting a blank cui file from the transfer tab
as the main cui and overwriting Custom.cui, if it was blank, these days.
--
R. Robert Bell
"James Maeding" wrote in message
news:5153086@discussion.autodesk.com...
Matt, mouse buttons do not behave if their definitions are not in the main
CUI.
So this locks you into not using a blank custom.cui as the main cui.
My solution is to copy the acad.cui to custom.cui, and not load an acad.cui
at all.
The custom.cui serves as both the user editable file and the provider of the
acad default stuff.
I hate this more than anyone knows.
Matt Stachoni
|>I think the solution with dealing with CUIs in a corporate setting is to
use Bob
|>Bell's approach.
|>
|>Which is, I believe, as follows (from memory):
|>
|>A) You have four major CUIs to deal with:
|>
|>acad.cui
|>acetmain.cui (express tools)
|>company.cui (your company's custom menus, toolbars, etc).
|>custom.cui (your users' personal CUI)
|>
|>B) You have two "modes" of Operation:
|>- CAD Admin, or "God" mode, where you can edit all of the CUIs
|>- User, or "The Great Unwashed" mode, where you can only edit your own
custom
|>(user) CUI.
|>
|>C) Create an "admin" profile that has acad.cui as the main CUI, with
company,
|>acetmain, and custom CUIs as partials.
|>
|>Edit them to suit your CAD Admin requirements.
|>
|>D) Create a "user" profile, which has the custom.cui as the main CUI,
without
|>any partial CUIs. Set your enterprise CUI to use acad.cui, with acetmain
and
|>company.cui as partial CUIs
|>
|>E) The user can create Workspaces under custom.cui to their heart's
content.
|>However they cannot edit anything under the Enterprise cui.
|>
|>In addition, as you note, because there is no reason a user cannot
circumvent
|>this, it's important that all corporate CUIs reside on the server and be
made
|>read-only to non-CAD Admin personnel. That's as easy as creating a single
CAD
|>ADMIN security group on your network's domain, assign yourself (and any
other
|>CAD Admins) as members, and assign this group Full Control on the
folder(s).
|>Assign everyone else Read Only permissions.
|>
|>Matt
|>mstachoni@comcast.net
|>mstachoni@bhhtait.com
|>
|>
|>On Mon, 24 Apr 2006 21:07:13 +0000, eloquintet <> wrote:
|>
|>>i had setup an enterprise cui and wanted to set it up so i created 2
profiles. 1 had acad as the main and enterprise as the enterprise (user).
the other had enterprise as the main and no enterprise (admin). i was told
that the only way to prevent users from creating a profile as i have and
opening up the enterprise cui and dragging elements into their main cui was
to only grant permissions to the the enterprise folder to certain users. ok
so we created permissions to only certain users but i had to move the
location to make it easier to assign permissions. now i open autocad and try
to change the path it will not allow me into the folder to path it. so do i
need to remove the premissions then path it then reassign the permissions. i
have no ability to assign permissions so everytime this happens i have to
involve IT which i would rather avoid. so i would like a better way of being
able to edit the enterprise than creating a profile and switching back and
forth. i would also like a
|>>way of protecting it from being opened other than assigning permissions
to the source folder. the problem is that i configure our machines because
our IT guys don't have time or knowledge to do it but i don't have time or
knowledge and will not likely be given rights to apply permissions on my
own. so i would like to have a way to truly make our enterprise read only
without involving IT.
James Maeding
Civil Engineer and Programmer
jmaeding - athunsaker - com
