Closed dannyrohde closed 1 year ago
Hi @dannyrohde ,
I'm afraid the removal of horizontal_margin
and vertical_margin
is final.
Those parameters have been changed (split) to margin_top
, margin_right
, margin_bottom
and margin_left
.
This brings the SingleColumnLayout
more in line with other LayoutElement
objects, with similar properties.
You can simply set those properties according to the following logic:
margin_left
and margin_right
ought have the value of horizontal_margin
margin_top
and margin_bottom
ought have the value of vertical_margin
That ought to be the same as what you've done previously.
If you really want these parameters to be the exact same as before, you can of course create your own class SingleColumnLayout2
and:
SingleColumnLayout
__init__
method in such a way that your class accepts horizontal_margin
and vertical_margin
Kind regards, Joris Schellekens
Describe the bug Reimplementation of
SingleColumnLayout
in release 2.1.16 breaks existing workflow as it removes previously used parametershorizontal_margin
andvertical_margin
.To Reproduce Up to 2.1.15, the following works:
From 2.1.16, the two parameters are not available any more and the code breaks.
I've tried to recreate the old behaviour by directly instantiating from
MultiColumnLayout
, but that doesn't produce the same formatting/layout as theSingleColumnLayout
did.Expected behaviour Existing code should not break with a bug fix update from 2.1.15 to 2.1.16.
SingleColumnLayout
should continue to support the parametershorizontal_margin
andvertical_margin
.I assume this change is unlikely to be reversed as there will likely have been good reasons to reimplement the class. In that case, could you please advise how to migrate the code in a way that horizontal and vertical margins can still be used with
SingleColumnLayout
? Or if I'm using it the wrong way, please advise.I've pinned 2.1.15 for now, as it works as expected.
Desktop (please complete the following information):
Additional context Couldn't find any documentation about the change apart from the 2.1.16 change log. GitHub Blame suggests the relevant code was changed with 2.1.16.