#5372 – Toggling between Flex and Sequence modes causes loosing layout info #5616
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
How the feature works? / How did you fix the issue?
This PR fixes the issue with data loss in the layout when switching from flex to sequence mode. The problem was that the
initialize
method of theSequenceMode
class called thereArrangeChains
function with theisSnakeMode = true
parameter, which triggered chain rearrangementUpdate:
isSnakeMode
is disabled only when switching modes. The layout will be still recalculated after sequence updates. To manage this, a new argumentneedReArrangeChains
has been added to theinitialize
method of theSequenceMode
Check list
#1234 – issue name