Can't turn off warning message in ME10 11.6

[Jfallert]

When a user is editing .mi files created in Annotation they get the warning: "You are going to break the associativity to the 3D model. Enter CONFIRM to continue or OFF to disable warnings."

If the user types 'OFF', when they get the warning. the prompt is not longer activated for that particular command, but the prompts continue for the other commands.

We've tried using the following commands in ME10 startup scripts to turn off the warning:

CHECK_3D_GEO_MODIFY OFF
CHECK_3D_GEO_MODIFY WARNING

using either one or the other, in either order... nothing happens.

Is there any way to shut off or deactivate this warning message for an entire session of ME10? The constant re-occurance gets to be a pain.

Thanks in advance,

Jeff

[John Scheffel]

The OFF option is the one you want. I'm not sure why it doesn't work, I thought it would stop these messages.

If no one comes up with a more elegant solution you might try the following. It is a macro that deletes most of the INFOs attached by Annotation. I'm haven't tested it with the latest release, but in older versions it would eliminate the modification warnings. Use with caution and save to a new file name after using it. It will completely destroy the associativity to the 3D Model and is irreversible.
DEFINE Nuke_adu_info
LOCAL Answer
BEEP BEEP
READ QUALIFIER STRING PROMPT
('WARNING: This will remove ALL associativity to the SolidDesigner model.'
+ ' Click CONFIRM to continue or END to cancel.') Answer
IF (Answer=CONFIRM)
CHANGE_GLOBAL_INFO 'SD*' ''
END_IF
END_DEFINE {Nuke_adu_info}
As a test you can just run the CHANGE_GLOBAL_INFO command from a command line. We assigned the macro to a menu button and added the warning since it is pretty destructive if you click it accidentally.

[H.annes]

Good morning!

It was a "feature" to increase the security in ME10 11.00 that loading of a new drawing sets CHECK_3D_GEO_MODIFY back to WARNING.

But in version 11.60B it is possible to switch off this warning for the whole session. You have to start ME10 with the option
-noannowarn
or set the environment variable
MENOANNOWARN=1
in "me10.ini"

(as written in the "technical appendix" of the "readme.html" in 11.60B)

Best regards from sunny Austria,
Hannes