Skip to main content
Known Participant
February 23, 2010
Answered

to get the dlgid of framemaker continue note alert

  • February 23, 2010
  • 1 reply
  • 569 views

What is the framemaker Api to use to get the dlgid of framemaker alert , so that I can close the dialog at runtime using F_ApiClose(dlgid, 0)?

This topic has been closed for replies.
Correct answer Russ Ward

Hi Asha,

You can't dismiss these dialog boxes programatically. This is a long-standing problem that has caused frustration for FDK developers, probably since the beginning. Your only hope is to prevent them from appearing at all, which in this case you should be able to do by setting FS_RefFileNotFound to FV_AllowAllRefFilesUnFindable for F_ApiOpen(), something like:

F_PropValsT openScript, *returnp = NULL;
UIntT sn;

F_ObjHandleT docId;

StringT path;

[. . . code to get the path . . .]

sn = F_ApiGetPropIndex(&openScript, FS_RefFileNotFound);
openScript.val[sn].propVal.u.ival = FV_AllowAllRefFilesUnFindable;

docId = F_ApiOpen(path, &openScript, &returnp);

One problem with this, though... it should prevent the warning you are seeing. However, it will not prevent that "Can't display some imported graphics" warning that shows when the missing graphic is scrolled into view. To my knowledge, that warning cannot be suppressed. If the missing graphic happens to be in the viewable area when the document is opened, your code will still be halted by that second message.

Russ

1 reply

Known Participant
February 23, 2010

I am getting the following framemaker alert note before closing the open documents and book in framemaker after saving the book as pdf.

"Cannot display some imported graphics. The images will appear as gray boxes." I am getting this message for framemaker 7.1 and not when working with framemaker 7.2.

How do we avoid getting this message ? Or how do we close this alert box programmatically without user intervention?

Russ WardCorrect answer
Legend
February 23, 2010

Hi Asha,

You can't dismiss these dialog boxes programatically. This is a long-standing problem that has caused frustration for FDK developers, probably since the beginning. Your only hope is to prevent them from appearing at all, which in this case you should be able to do by setting FS_RefFileNotFound to FV_AllowAllRefFilesUnFindable for F_ApiOpen(), something like:

F_PropValsT openScript, *returnp = NULL;
UIntT sn;

F_ObjHandleT docId;

StringT path;

[. . . code to get the path . . .]

sn = F_ApiGetPropIndex(&openScript, FS_RefFileNotFound);
openScript.val[sn].propVal.u.ival = FV_AllowAllRefFilesUnFindable;

docId = F_ApiOpen(path, &openScript, &returnp);

One problem with this, though... it should prevent the warning you are seeing. However, it will not prevent that "Can't display some imported graphics" warning that shows when the missing graphic is scrolled into view. To my knowledge, that warning cannot be suppressed. If the missing graphic happens to be in the viewable area when the document is opened, your code will still be halted by that second message.

Russ