Application Notes

OneSpace Designer Modeling

Saving & Loading of Customization Files :

If the following check-box is set (by default it is set) all current settings will be saved into the operating system registry when user exits from SolidDesigner :

To see how it looks like, run "regedit"  and find Registry Entry

    HKEY_CURRENT_USER\Software\CoCreate\OneSpace Designer\Version\Language

Advantage :

• User does not have to do anything special to restore the last settings.
• Everytime user restarts OSD, the current settings will be read from here automatically
• It is a good method to keep different settings for different users on the same computer

Disadvantage:

• The registry setting is not in a user-readable format
• We cannot copy the settings from one user to another user
• We cannot save  registry entry to restore it again if needed

But if you want to :

• Make a company-wide customization and copy it for all users
• Return to a certain-customization after trying-around or re-installing Windows ..etc

.. then you must create readable ASCII-customization files !

To do this select menu :

[EDIT]

  [Settings]

     [UI-Settings]

and select [Export Customizations]

OSD will show you where the files will be saved.

Now users can experiment to find the best setup for them, and can then "freeze" this state by exporting the customizations to definition files which can then be made available to all users at a site or within a company.

!! These files will not be read automatically at startup  !!

!! If above registry entry exists, OSD will always read the customization from the registry not from the saved-location !

If you want that the ASCII files are read instead of the registry, you have 2 methods :

• Run regedit and simply delete the registry entry
• Run OSD bat-file “ResetUISettings.bat” under OSD-directory

After this step, start OSD again.

OSD will not find any registry entry and will read (if exist) ASCII files from the saved-location.

Warning :

Please keep in mind that Toolbar location information is not stored together with the ASCII-files but only inside registry !

After loading the ASCII-Files the previous toolbar locations are unfortunately lost. You must re-locate them and quit & restart OSD once so the values are again inside registry.
What is the command   [Reset] / [Reset All]   inside Customize-Menu ?

[Reset] / [Reset All] resets only contents of toolbars !!

After the operation, the number of toolbars stay the same on the screen.

A deleted toolbar will not come back again  or an added toolbar will not disappear !

If you edit contents of a toolbar (add/delete entries), with  [Reset]/[Reset All] you can reset the contents to the last saved-values.

How can I take over my customizations from one OSD version to another ?

! ! Don’t  make changes to original OSD toolbars and menus but create your own.
A new version could have added functionality and you don’t want to overwrite them with your own commands.
By creating your own toolbars, you will always have original toolbars of new version  correctly.

! ! Split customizations into 2 groups.

·         Company-wide

·         User-specific

To create company-wide customizations for all users :

1) Export the customizations

2) Copy them into a special directory   e.g   C:/MIP/sd_all_cust/

3) Delete the files, which are from OSD  (they start with “win_”)  and keep only the files which are your customizations for all users (company-wide).

The ones you should keep are :

*.tlb      à  toolbars

*.pum    à right-mouse button menus

Rename the file “user_avail_cmds.cmd”  to “sd_avail_cmds.cmd”

user_filer_project_dirs  à your project directories

*.acc  à keyboard shortcuts

*.bmp  à icons

4) Set environment variable :

SDSITECUSTOMIZEDIR=C:/MIP/sd_all_cust/

This means, first files in this directory will be read, later users own customizations.

Inside this directory, you can also create a file called "site_startup".

Inside you can put commands which will be called at startup time of OSD.

To execute commands for Annotation, create a sub-directory “Annotation” and use the Annotation-startup file "am_customize".

5) To create user-specific customizations, we should do the opposite like in step 3.

After exporting, delete all which are not user-specific – e.g all original toolbars, menu-definitions etc – leave only user-specific files inside.

After installing the new version, export customizations – this will create a new directory.

Delete the contents of this directory and copy the user-specific files from the previous version to this directory.

Delete registry entry of the new version ( run “regedit” or use “ResetUISettings.bat” ) and restart OSD.

Reposition toolbars and exit OSD – this writes again to the registry.

Advantages of this method :

·         Company-specific customizations are in one location – outside of OSD installation directory. They will only be edited centrally.

·         A new version of OSD can start using them immediately

·         Original OSD files are not edited.