So I've figured out/remembered why I added that flagging. I had one location checking it unnecessarily that I've pushed to master, but when determining the available space to fit the text into (https://github.com/shoes/shoes4/blob/master/lib/shoes/swt/text_block_fitter.rb#L83-L89), we need to know whether we're moving down a line or not to do it right. `current_position` didn't have the right information on it without this flag (or some other change...)

The reason is rooted in the ordering of the slot's logic. It's sequence goes:

1) Slot decides whether to move down or not
2) Slot sets position on the element but doesn't update `current_position` values
3) Slot optionally calls `element.contents_alignment` to get element sizes calculated
4) Slot modifies `current_position` based on the resulting element absolutes

In 2), the slot knows moving down, but without my flag, you can't tell based on `current_position`. That meant that during 3), within `element.contents_alignment` we didn't know whether we're fitting in the current or next line.

Does that make sense? Is there some other, more elegant change we could make to the `current_position` to give the right signal? It feels like maybe something about the position could be updated at that point to give `contents_alignment` the right signals without the bool, but it isn't clear to me what that would be (or what the consequences would be)