Skip to main content
T
TimSharp1-Visitor
1-Visitor
March 1, 2011
Solved

Can you suppress warning messages when creating CGM files?

  • March 1, 2011
  • 1 reply
  • 3169 views

When we have finished or amended each of our Isodraw drawings, we export a CGM version of the file for use by our authors.

We never edit CGM versions of our drawings, they are just used as a convenient format to add to Word documents.

We've found through experience that an old version of CGM works best for us - "Model Profile (ISO 8632:1992/Am.1: 1994)".

But, because it is an old format, it pops up an error message saying it doesn't support things like callouts or object infos.

I have a macro that creates the CGM files and saves them in the right directory, but it always pops up the warning message. Is there a way to suppress the error message?

    Best answer by bgraffmann

    You can switch off ALL dialogs (not only the warnings!) by

    app.interaction = false

    Please make sure to switch that on again by

    app.interaction = true

    after your export command, because the setting is not limited to the macro execution.

    1 reply

    T
    thendricks12-Amethyst
    12-Amethyst
    March 1, 2011

    Could you post a sample Iso file?

    T
    TimSharp1-VisitorAuthor
    1-Visitor
    March 1, 2011

    It happens with any Isodraw file that has callouts on it. It's because we're using an old CGM standard that it comes back with warning messages that there's "No support for callouts" or for several other newer features of Isodraw that are not supported by that standard.

    The CGM files are fine for our purposes, I just want to suppress the warning message that pops up every time we create a CGM file.

    We've tried using newer CGM standards, but they all cause problems with the version of Word we use, so we're stuck with the old one "Model Profile (ISO 8632:1992/Am.1: 1994)".

    B
    bgraffmann1-VisitorAnswer
    1-Visitor
    March 2, 2011

    You can switch off ALL dialogs (not only the warnings!) by

    app.interaction = false

    Please make sure to switch that on again by

    app.interaction = true

    after your export command, because the setting is not limited to the macro execution.

    Terms & ConditionsAccessibility statement