Config option pro_colormap_path not loading appearance.dmt at launch

[tbraxton]

Creo continues to be inconsistent with specifying path names inclusive of spaces. Using the config option pro_colormap_path requires putting the path within quotes(") if there are any spaces in the path names.

system_colors_file D:\ProE Standards\System Colors\syscol_wf.scl
pro_colormap_path "D:\ProE Standards\Color Maps"
mdl_tree_cfg_file D:\ProE Standards\Start Creo4\tree.cfg

Note that the other two options listed have spaces in the path names and do not require the double quotes to work properly while the colormap options does not work for me in Creo 4 M110 without quotes. Holdover from the UNIX rules, not acceptable in an application that has been claiming to be MS Windows compliant for a long time. Has anyone else seen this behavior on any other options in Creo 4 or higher?

[tbraxton]

Does anyone else find that this is absurd? This bug has been open for nearly a decade and either has resurfaced or has not been corrected. Does any one else have any experience with this?

Creo 1.0

Created: 14-Apr-2011 

• Reported to R&D as SPR 2831129
• Inserting double quotes ( " " ) before and after the option value allows to load the color map file

[BenLoosli]

Been around long enough that we don't use spaces in folder names when dealing with PTC paths.

A lot easier to name a folder with no space than rewriting hundreds of lines of code, verifying that you got all locations, testing the code and getting it rolled into an update.

Don't misread this! I do agree that the code should be 'MS-compliant' but on such a trivial matter, it will get updated eventually when something else bigger forces a change. Maybe the 31 character file name limitation will fix spaces in folder names, too. BTW: Creo 4 was supposed to fix the spaces issue!

[KenFarley]

As Ben does, I got in the habit long ago of not using spaces in my directory specifications for ProE -> Creo. They're all something like C:\ptc\DefaultFiles\drwsetup.dtl . The place where the space character issue is most noticeable for me is in my search path designations (search.pro). I have all the entries in there specified with quotes around them.

As far as this being a Unix carry-over, perhaps, but if you've done any batch programming for Windows you will be familiar with the need to use quotes (sometimes nested doubles and singles) to get things with spaces in them to be properly handled. Stems from the ancient characterization of the space character (and tab, newline, etc) as "whitespace". They're designators of the transition from one token to the next when parsing commands. Definitely makes programming a lot less straightforward than one might wish. Pretty much guarantees that anything besides the simplest batch file will take some iteration to make it work.

[remy]

This is addressed with the following article: https://www.ptc.com/en/support/article?n=CS20659

If you still need to live with both worlds (with space char and without), one trick is to use symbolic links: https://en.wikipedia.org/wiki/Symbolic_link