Custom Tricks

.CCTR [Sections]

Each ControlCenter stores its configuration information in a .CCTR file located in the directory where Object Desktop was installed (typically x:\Program Files\Object Desktop\ControlCenter). Here a few undocumented tricks that can be used to customize your ControlCenters:

 

For example, a typical .CCTR file may start like this:

[Sections]
Section=Task Browser
Section=B:Desktop

In addition to adding items via drag-and-drop from the desktop, additional items can be added manually. Environment variables that are defined on the system can also be used in place of an absolute path reference. For your convenience, the installation of ControlCenter defines a %CC_ROOT% environment variable that contains the directory where ControlCenter was installed (note: due to limitations of Windows 95/98 systems, this environment variable is only available after rebooting). Other useful environment variables include %SYSTEMDRIVE% (the drive Windows was booted from, e.g. C: for Windows 95/98 systems and possibly a different drive for Windows NT). %SYSTEMROOT% can be also be used. It points to the "top level" directory where Windows was installed (typically of the form C:\Windows or X:\WinNT).

 

Universal Naming Convention (UNC) paths, URL objects, data files, and "executable" system files (including .CPL Control Panel files) can all be referenced in this manner (the .CCTR files are case insensitive). For example:

[Sections]
Section=B:%CC_ROOT%\FIND.EXE" [the closing " is necessary with the CCROOT variable]
Section=B:%SYSTEMROOT%\SYSTEM32\CMD.EXE
Section=B:%SYSTEMROOT%\SYSTEM32\TWEAKUI.CPL
Section=B:%SYSTEMDRIVE%\Windows\EXPLORER.EXE
Section=B:D:\MyImageFile.JPG
Section=B:\\NTServer\Development
Section=B:\\NTServer\Access\MyLinks.url

.CCTR [Options]

The cross-hatching on virtual desktops can be disabled by adding the following entry to the [Options] section of a .CCTR:

[Options]
UseCrossHatch=0

To disable the RMB access to the Properties menu of a ControlCenter:

[Options]
ShowMenu=0