Trail to replace Syscol

Where is the config.pro file that the company is automatically replacing? You can have more than one config.pro. 

The main location is typically in the <loadpoint>/text folder.

Another is the startup folder (you can determine this by launching creo and seeing what the original working directory is or looking at the icon properties you use to launch creo and seeing what the  "start in" folder is.

If you are having permission issues due to config.sup or other corporate IT controls you can make a mapkey that will load the syscol file. This is not as convenient as an automated batch sequence but is better than doing it manually if you are blocked form implementing the batch file.

There a bunch of ways to accomplish what you're trying to do. Keep in mind that you can load config files after startup. Config files that are loaded last will overwrite what was previously loaded (unless locked in the .sup). In this case, it might be easier for you to load a config after startup that points to your custom colors file. If you want to get a little fancier, you could automate the process with a mapkey.

The config file that you load should contain a line that points to your system colors file:

system_colors_file $USERPROFILE\CreoX\configs\syscol.scl ----- This is an example. Your path would be different.

Another option would be to write a mapkey that adjusts the colors in your current session but doesn't save it. Something like this:

!!!CHANGE BACKGROUND TO WHITE
mapkey LIGHT @MAPKEY_LABELBACKGROUND COLOR WHITE;\
mapkey(continued) ~ Command `ProCmdRibbonOptionsDlg` ;\
mapkey(continued) ~ Select `ribbon_options_dialog` `PageSwitcherPageList` 1 `colors_layouts`;\
mapkey(continued) ~ Select `ribbon_options_dialog` `colors_layouts.Color_scheme_optMenu` 1 `2`;\
mapkey(continued) ~ Activate `ribbon_options_dialog` `OkPshBtn`;

Because I have a path to a different system colors file in my local config, running this mapkey reimports the system colors file I have locally.

!!!CHANGE BACKGROUND TO DARK (CUSTOM)
mapkey DARK @MAPKEY_LABELCHANGE BACKGROUND TO DARK;\
mapkey(continued) ~ Command `ProCmdRibbonOptionsDlg` ;\
mapkey(continued) ~ Select `ribbon_options_dialog` `PageSwitcherPageList` 1 `colors_layouts`;\
mapkey(continued) ~ Select `ribbon_options_dialog` `colors_layouts.Color_scheme_optMenu` 1 \
mapkey(continued) `Custom`;\
mapkey(continued) ~ Activate `ribbon_options_dialog` `OkPshBtn`;

Hope this helps!

Ty

---

@Coin37coin wrote:

Hello all.

 

I'm trying to have my own environnement in Creo .... (I hate the dark font color !)

I know, it simple, you need to register it and save the syscol in your config.pro. Problem is that my company don't allow it : every time i start Creo, it suppress the old config.pro and replace it by the standart one.

 

So I try to creat a batch who execute my company batch and then replace the syscol.scl. To do it, i created a trail who made that task

Unfortunatly, each time i start by batch, he never execute my trail. What i'm doing wrong ? Maybe there is a simpliest way to do it ? 

 

What's inside my batch :

@echo off
H:\proc_sh\cae\start_creo5.bat "P:\Couleur.txa" %*

 

 

---

Hi,

I guess that H:\proc_sh\cae\start_creo5.bat does not use argument no.1, i.e. "P:\Couleur.txa".

If you can please upload the contents of H:\proc_sh\cae\start_creo5.bat file ... I can check its contents.

Go to FILE - OPTIONS - CONFIGURATION EDITOR.

At the top, in the box labeled SHOW:, click the down arrow. This lists the config files you are using.
You can have MORE THAN ONE config file.

My system loads our company standard config.sup file (these are the "unchange-able" options)

It then loads the company standard config.pro file (these are the options the company wants me to start with but are changeable)

It then loads my config.pro file which is my personal settings that make creo run the way I want. For example, this is where my syscol file is called for, also where my mapkeys are and others I want to use.

This is why I asked "where is the config.pro files". There is NOT just ONE config file.