🚀 go-pugleaf

More layout that I don't understand.

Several of the "big" blocks in my documents are <para>, <screenshot> and <tabula>. They're self-explanatory: container, graphic and table respectively.

The problem I am having is that wherever my XML contains a <tabula> followed by a <screenshot>, the graphic is appearing first. Where the XML contains a sequence of alternating <tabula> and <screenshot> elements, all the screenshots appear followed by all the tables. However if there is anything at all in the XML between the <tabula> and the <screenshot>, they appear where I expect them to, e.g. table, para, screenshot.

All my table designs are defined with:
 spaceAbove = 12pt, spaceBelow = 12pt
 LI = RI = 0cm
 align = Left, start = Anywhere

The relevant read/write rules are:
 element "screenshot" {
  is fm graphic element;
  writer facet default specify size in pt;
  attribute "src" is fm property file;
  fm property import by reference or copy value is "ref";
  fm property alignment value is "acenter";
  fm property position value is "below";
  fm property horizontal offset value is "0pt";
  fm property vertical offset value is "0pt";
  attribute "height" is fm property height;
  attribute "width" is fm property width;
  attribute "dpi" is fm property dpi;
 }

I could speculate (dangerous, but the doco isn't helping me much) that the problem is that both tables and graphic objects place an insertion point at the end of the preceding element (I can see this insertion point before the end of paragraph marker above the image or the table), and the graphic object, being placed "below" the insertion point, is taking priority over the table (which is placed "anywhere"). Am I right?

Whether right or wrong, is there anything I can do to fix this - short of inserting empty paragraphs everywhere that that I have images preceded by tables?

Incidentally, they're not <tabula> elements, but we're not allowed to see < t a b l e >. (That* doesn't need explaining!)

Thanks
Trevor