bug stack order

[MB365]

Issue captured: Currently scheduled (not confirmed yet) for 23.6 release in Plus editions.

Workaround: Group objects, arrange up or down, and then Ungroup as needed.

[handrawn]

Hi Matt - will the perpetual version get bug fixes ?

as far as this bug goes, I looked at it with two and then three objects selected, it appears to toggle - if so then a possible quicker way to work round is to just repeate the operation so that it then toggles back again to the required stack order eg:

ctl+B ctrl+F ctrl+B instead of just ctrl+B

this avoids grouping which can add complication

[Acorn]

ctl+B ctrl+F ctrl+B instead of just ctrl+B

handrawn, I had thought of and tried that but you need to keep an eye on the direction of required travel so the cadence would be either Up-Down-Up or Down-Up-Down.
Group-Action-Ungroup has no consequences if all the selection is on the same Layer, which is implicit in this activity. To avoid any such cross-layer conflict, you could also go Solo mode.
[Grouping flattens the grouped items into the topmost item's Layer]

@Matt, by not mentioning a bug release for v20 Perpetual, you appear to be disenfranchising many. Why buy something that requires you to buy an upgrade a year on?

Acorn

[handrawn]

handrawn, I had thought of and tried that but you need to keep an eye on the direction of required travel so the cadence would be either Up-Down-Up or Down-Up-Down.
Group-Action-Ungroup has no consequences if all the selection is on the same Layer, which is implicit in this activity. To avoid any such cross-layer conflict, you could also go Solo mode.
[Grouping flattens the grouped items into the topmost item's Layer]

agreed...

... and I have just noticed strange things happening in my test file with shift+ctrl+B where it goes to the stack bottom rather than where it should be

@Matt, by not mentioning a bug release for v20 Perpetual, you appear to be disenfranchising many. Why buy something that requires you to buy an upgrade a year on?

Acorn

I hope this is just symptomatic of there not yet being a pipeline for XDA Perpetual bug fixes, and that one is imminent; otherwise we have not really advanced that much from the bad old days have we....

[Acorn]

As at v23.7, the Move backwards (Shift+Ctrl+B) is still acting as a Put to Back (Ctrl+B) when there are just three objects involved.
@Xara - another JavaScript counting FAIL?

UPDATE:
15 minutes later Xara released v23.8 and the bug was corrected.
@Xara - thank you.

Acorn

[MB365]

As at v23.7, the Move backwards (Shift+Ctrl+B) is still acting as a Put to Back (Ctrl+B) when there are just three objects involved.
@Xara - another JavaScript counting FAIL?

UPDATE:
15 minutes later Xara released v23.8 and the bug was corrected.
@Xara - thank you.

Acorn

Very timely to revive this thread on the same day of a release.

[Acorn]

Very timely to revive this thread on the same day of a release.

Matt, it was @ChrisM's frustration over flagging broken Web animations when Sticky was used & not being able to apply the same on a popup layer...

Acorn