Jonathan Osuch wrote:
Paul,
Around page 124, under "5.5 Startup Parameters", where it states:
COMMENT=[comment1]/[comment2]/[comment3]/[comment4] Inserts comments into PAR files. These comments can include variables that are expanded at the time the PAR file is created. Variables are indicated by $varname$. Underscore characters are expanded to blanks. If you want to include the special characters '$', '_', or '\' in a comment, precede the character with '\'.
Should that not be a '/' for the special character that might need to be replaced, instead of a '\' ??
Using a back-slash is pretty standard to indicate a special character. And, it does work in Fractint. The forward-slash is being used to indicate the start of the next comment line, so we can't use it to indicate a special character.
So actually, both the forward and backward slashes are "special characters". One is used as a COMMENT delimiter between each line of comments created. And the other is used to indicate that the following character is another special character. And if someone wanted to include either of these slashes into their comment lines they would need to specify the following: COMMENT=\/ ...to get a forward slash without a new comment line. COMMENT=\\ ...to get a backward slash. Which would mean the FractInt Document should specify both types of slashes as special characters??
Xfractint ignores everything after the back-slash. I'll look into fixing Xfractint after this patch is released.
I did not realize XFractInt was not handling this correctly.
Thanks for your comments.
You are more than welcome. :-) Sincerely, P.N.L. ------------------------------------------------- http://home.att.net/~Paul.N.Lee/PNL_Fractals.html http://www.Nahee.com/Fractals/