This is a feature idea.
I am loving the way the absolute positioning is working on the visual editor, but there's one particular instance where it can make things difficult. If I do not know the length of my data, and the data needs to wrap, it can overlap my next elements.
So, consider two elements
[Wrapping Text for 1–12 lines - absoluteY: 10]
[Next Print - absoluteY: 30]
In that case, "Next Print" would end up being overlapped as soon as the first element grew past 1-2 lines.
One idea I had that might work, is to add a boolean "☑ Use Flow-Based Rendering" (not set on the name). Then I would check that option on the "Next Print" line.
The benefit to this, is that the visual editor could still use Next Print's absoluteY for showing it on the editor, but at the point it was rendered, it would just be rendered after the previous element, similar to how the code-based version typically works.
This is a super low priority thing for us, I've only run into wanting this a couple of times and have always been able to work around it. I'm just throwing the idea out there in case you feel it has merit.
This is a feature idea.
I am loving the way the absolute positioning is working on the visual editor, but there's one particular instance where it can make things difficult. If I do not know the length of my data, and the data needs to wrap, it can overlap my next elements.
So, consider two elements
In that case, "Next Print" would end up being overlapped as soon as the first element grew past 1-2 lines.
One idea I had that might work, is to add a boolean "☑ Use Flow-Based Rendering" (not set on the name). Then I would check that option on the "Next Print" line.
The benefit to this, is that the visual editor could still use Next Print's absoluteY for showing it on the editor, but at the point it was rendered, it would just be rendered after the previous element, similar to how the code-based version typically works.
This is a super low priority thing for us, I've only run into wanting this a couple of times and have always been able to work around it. I'm just throwing the idea out there in case you feel it has merit.