IDCS5 Win - Constant appearance of assert and how to fix it.

I have a section of the code that produces the following worth up to fifty times a race, which is, of course, annoying:

"No command name class kMergeStoriesCmdBoss, which goes on the undo stack."

He then CITES CommandProcess.cpp (3126)

When I'm not in the code, the assertion appears whenever I execute the following line:

Connects two blocks of text so that the text overflows from one to the other.

Utils < ITextUtils > ()-> LinkTextFrames (LastFrame, NextFrame, kFalse);

I looked to see if there's a call that I have to set the name and there is no ITextUtils.  I have also studied (just in case) IMultiColumnTextFrame.h without success.

Is it possible to get this annoying and time consuming State to stop the spread upward?

R,

John

In my humble OPINION - the correct way to code anything which could make several orders is to run the whole thing in your own sequence of commands.  This means that the user can cancel the entire operation in a single action and also has the effect of putting your name of command sequence on the undo stack (thus avoiding an unnamed entry).

Ian

Tags: InDesign

Similar Questions

Maybe you are looking for