IsoDraw seems to have this behavior backed in of pointing and yelling very time it encounters CGM Application Data that isn't intended for it. Rather than silently skipping that content (as the CGM specification says a consumer of CGM should do), IsoDraw writes a log file for the image. This makes for an annoying mess of pointless log files.
Why is it a file reader/displayer like IsoDraw sees it as default necessary to write files to the file system?
Anyway, I'm hoping there might be a command line parameter, or registry hack to get IsoDraw to just shut up.
Here is an example of the noise:
filename.cgm.LOG
### BEGIN: 2/7/2022, 2:47:22 PM ###
*** Protocol of: 7.2.2022, 14:47:22 *** Program version: 7.3 M030 ***
Import of file:filename.cgm
File format:CGM
Start of conversion
Skipped element (Class, No., Size, Count): 7 2 54 1
End of conversion
### END: 2/7/2022, 2:47:22 PM ###
Solved! Go to Solution.
Hi,
Try this solution: "Remove the system environment variable FLEXLM_DIAGNOSTICS 3".
Hi,
Try this solution: "Remove the system environment variable FLEXLM_DIAGNOSTICS 3".
There is no FLEXLM_DIAGNOSTICS system variable set. (at least not per command prompt "set" query).
Is there something that can go into the OptCGM.prf file ( in C:\Program Files (x86)\PTC\PTC Arbortext IsoView 7.3 ) ?