New gap field

[nopeslide]

Introduce a new field that simply draws a gap of the specified height between two rows and a centered text.
I.e.
gap(1cm)[] or gap[] for some small default length (maybe 5pt + text height?)

If specified between two fields of the same row, draw blank fields after the previous field until the end of the row
draw the gap and in the next row start with blank fields up to the column of the field after the gap.

without gap:

bits(3)[XXX], bits(3)[OOO]
|XXXOOO|

with gap

bits(3)[XXX], gap[text], bits(3)[OOO]
|XXX   |
| text | 
|   OOO|

[jomaway]

If i understand you correct this similar to the Multi break field in the example. Just with a custom row high?

Would kind of use case do you have in mind with this?
Adding a field bits(bpr)[Text] with bpr being the size of the bits per row will result in a multibreak like in the example, just without the option to specify the row high.

Being able to define custom highs per row is something we need to look into. Maybe just a rows argument on bytefield would do which is later passed to tablex rows.

[nopeslide]

Would kind of use case do you have in mind with this?

Drawing a gap to break the reading flow and visually indicate some change,
optionally with additional text acting as some kind of header

Adding a field bits(bpr)[Text] with bpr being the size of the bits per row will result in a multibreak like in the example, just without the option to specify the row high.

From the layout perspectives, yes,
but without the borders and without specifying any size.

Being able to define custom highs per row is something we need to look into. Maybe just a rows argument on bytefield would do which is later passed to tablex rows.

Specifying a general row height in tablex, makes it harder to change them on a row by row base, doesn't it?

[jomaway]

Specifying a general row height in tablex, makes it harder to change them on a row by row base, doesn't it?

Hmm, guess it depends, i more thought about passing an array to tablex, similar like the pre and post cols.
This array can then be automatically generated by bytefield or passed through from the user. Something like this. But maybe it is not as trivial.

But actually for rowheaders we need a similar approach. with adding rows without border in between.