Undo 'Image Size...' does not restore shape positions

Is something not working like it should? Let us know.
User avatar

2018-03-06 22:06:50

(Pixelmator Pro 1.0.8 on macOS 10.13.3 on a MacBook (Retina, 12-inch, Early 2015))

Starting with this group of shapes (7123px x 2000px) (I know – the gap between the Y and the o still needs tweaking):


I resize to 712px x 200px for export and get this:


I then undo the resize because I want to keep the original image size and get this:

User avatar

2018-03-07 09:57:33

I reckon this bug might happen, in one way or another, with undoing image size changes in an image with layer groups whether they're pixel, shape, or text layers. There are quite a few fixes for groups that we're working on, so this should be included as one of them.
User avatar

2018-03-22 12:41:56

Hi Andrius,

I'm still seeing this in Pixelmator 1.0.9. Did the group fixes not make it into this build? Or have they not fixed this particular problem?

Let me know if you need more info. If so, I'll post a list of steps to reproduce the bug.


- Stef.
User avatar

2018-03-22 12:48:55

This version doesn't include a fix for this particular problem — it's coming a little later as a full fix for all the related bugs requires a bit more work.
User avatar

2018-03-22 13:21:06

Thanks for letting me know. I'll tread carefully around this feature until then.
User avatar

2018-03-22 16:28:37

I'm getting this too. Whenever I resize artwork to export for web, when I try to revert to the original size, not all the elements return to the new size.
User avatar

2018-03-22 16:57:30

Hi Jonnie.

While this bug is still out in the wild, there are three things I'm to protect myself (depending on what is most convenient):
• Work at final size more often (if convenient).
• Resize the exported image rather than the source.
• Undo the resize by using Image Size... and entering the original dimensions rather than Undo to size back up.

Hopefully this will get fixed soon.

- Stef
(written about Pixelmator Pro 1.0.9)
User avatar

2020-03-10 10:37:26

This happens to me all the time and is extremely frustrating. And I'm on 1.5.5 !!
User avatar

2020-03-10 17:19:58

This should have been fixed quite a while ago and I'm not able to reproduce it using the steps provided by Stef originally — do you happen to have a different set of repro steps? Or could you possibly share a screen recording demonstrating the issue?