Migration and migraines need help

It looks like I am being forced into migrating to CE and windows 10. Neither are my favorite.

I find ce to be non productive but it’s time to teach this old dog new tricks. But forget they keyboard shortcuts not interested

im a one man shop I don’t need micro stations workspace to be as difficult as it is. I want the same setting for each project 

I only need folders set up for each project just like v8 .less is more. I’m sure I’ll change my mind but for now I want it easy.

next I need to simplify the menu

1 they take up way to much screen space

2 there are too many mouse clicks or keystrokes.

 I customized my main menu bar in v8ss and would like to implement these customizations and collapse the  new ribbon.

My customizations were like the old bar menu.ma 

how do I get these into ce

i also customized my shift tentative and right click button menus I need to import these

Parents
  • (This assumes you're using MicroStation CONNECT with the default installation)

    On the workspace, copy your v8i workspace components into the appropriate folders in:

    C:\ProgramData\Bentley\MicroStation CONNECT Edition\Configuration\Organization

    Put your variables in the standards.cfg file in that folder.

    You can not copy from your v8i config:

    1. MDL apps (.ma & .dll files) - you need to find versions specifically compiled for CONNECT or come up with a new workflow
    2. Macro basic (.BAS & .BA files) - these won't work anymore. need VBA replacements

    In the folder C:\ProgramData\Bentley\MicroStation CONNECT Edition\Configuration\WorkSpaces

    create a folder (call it Kirk or whatever). Create a text file Kirk.cfg (as long as the cfg file has the same base name as the folder). This file can be empty but must exist.

    Create a Worksets folder inside the Workspace folder you created. Create a folder inside the Worksets called AllProjects. Create an AllProjects.cfg (again, base name must match the folder). And again, this file can also be empty.

    (So something like C:\ProgramData\Bentley\MicroStation CONNECT Edition\Configuration\WorkSpaces\Kirk\Worksets\AllProject)

    Now all your standards are in the Organization level, you have a Kirk Workspace and an AllProjects workset that do nothing.

    Caveat: If you're planning on using the DGNWS file for things like like the sheet index and sheet number/titling, this probably isn't what you want. You'll want multiple worksets for that, but this will let you do that and still let you have all your standards in one place for all projects.

    EDITED: clarified the folders inside the workspaces a bit.

     

Reply
  • (This assumes you're using MicroStation CONNECT with the default installation)

    On the workspace, copy your v8i workspace components into the appropriate folders in:

    C:\ProgramData\Bentley\MicroStation CONNECT Edition\Configuration\Organization

    Put your variables in the standards.cfg file in that folder.

    You can not copy from your v8i config:

    1. MDL apps (.ma & .dll files) - you need to find versions specifically compiled for CONNECT or come up with a new workflow
    2. Macro basic (.BAS & .BA files) - these won't work anymore. need VBA replacements

    In the folder C:\ProgramData\Bentley\MicroStation CONNECT Edition\Configuration\WorkSpaces

    create a folder (call it Kirk or whatever). Create a text file Kirk.cfg (as long as the cfg file has the same base name as the folder). This file can be empty but must exist.

    Create a Worksets folder inside the Workspace folder you created. Create a folder inside the Worksets called AllProjects. Create an AllProjects.cfg (again, base name must match the folder). And again, this file can also be empty.

    (So something like C:\ProgramData\Bentley\MicroStation CONNECT Edition\Configuration\WorkSpaces\Kirk\Worksets\AllProject)

    Now all your standards are in the Organization level, you have a Kirk Workspace and an AllProjects workset that do nothing.

    Caveat: If you're planning on using the DGNWS file for things like like the sheet index and sheet number/titling, this probably isn't what you want. You'll want multiple worksets for that, but this will let you do that and still let you have all your standards in one place for all projects.

    EDITED: clarified the folders inside the workspaces a bit.

     

Children