🚀 go-pugleaf

For years, I've used a RunPages function to flow overset text. One thing that such a function must do is detect a permanent overset condition and stop. The test I have in the function is to test to see (a) if the frame is still overset and (b) if the frame contains no characters.

I don't know why it has taken me this long to realize that this is an inadequate test. A text frame that contains only a part of a long table also has no characters. So, if my function were used to flow a story that contained such a long table it would fail because it would erroneously decide that the story was permanently overset the moment it got to a text frame in the middle of a long table.

Has anyone else run into this? And if so, did you find a solution?

I've posted the text of my function before, but I'll put it here again in the first reply for easy reference. I think were I writing it today I'd probably break it down into more function calls but on the principle that it wasn't broke I haven't done that. Only now I realize that it is broke.