Affinity Photo/Transforming doesn't work?

[xmahlerx]

Hi, 

Newbie here, please bear with me. I've desperately tried and searched for this, it might be a bug but I'm more inclined to the explanation that I am utterly stupid.
Anyhoo, it happens mostly to pixel layers but it includes curves sometimes as well. When I try to copy something from another group or file, the layer, after it's selected with the move tool should be shown with points for resizing (screenshot 1), but it is shown without any such transform guides/points (screenshot 2). 

Did I accidentally press something? Am I demented?
Any help or tip will be much appreciated! 

[Pšenda]

Full-app screenshots, i.e. with the view of the Tool panel, or with the view of the Layers panel, would be suitable. Ideally, a video with a procedure that you perform and which does not work according to your expectations.

Do you really have the Move Tool selected?

[xmahlerx]

17 minutes ago, Pšenda said:

Full-app screenshots, i.e. with the view of the Tool panel, or with the view of the Layers panel, would be suitable. Ideally, a video with a procedure that you perform and which does not work according to your expectations.

Do you really have the Move Tool selected?

Hi Pšenda,

nice to see another Prague resident around here. :)) For clarity I'll stick to English though.

I do really have to Move tool selected. It didn't happen for me until I've upgraded to 2.2.1 but I haven't seen any bug report describing the same issue. I've screen recorded the process

It's a "zapeklitá situace"

[Pšenda]

6 hours ago, xmahlerx said:

It's a "zapeklitá situace"

Jak praví klasik, "Je to takový ošklivý, zlý, nepěkná věc" 🙂

It's not weird at all, because you Rasterize the shape (for what reason?), so you convert it to a Pixel layer, and of course it can't be transformed like other vector objects - that's why the frame changes too.
 

P.S. Just a piece of advice for the future - the recording of such a large screen is quite unreadable on smaller screens (I had no chance to see what you were doing on the tablet). If you ever need help with recording, it would be more practical to make the application window smaller, rearrange the workspace, and record from the viewport.

Edited November 24, 2023 by Pšenda

[Hangman]

19 minutes ago, Pšenda said:

It's not weird at all, because you Rasterize the shape (for what reason?), so you convert it to a Pixel layer, and of course it can't be transformed like other vector objects - that's why the frame changes too.

[Pšenda]

Well, it's not in Rasterization 🙂 (somehow I assumed that only the Image layer can be transformed).

You are using Artboards, so the document was not created in APhoto. Does it only do this in this document, or in every one, even without Artboards?

[Hangman]

26 minutes ago, Pšenda said:

You are using Artboards, so the document was not created in APhoto. Does it only do this in this document, or in every one, even without Artboards?

[Pšenda]

1 hour ago, Hangman said:

 

My question is of course directed at the OP who is having problems. Not for general functioning, where of course it works.

[xmahlerx]

3 hours ago, Pšenda said:

Jak praví klasik, "Je to takový ošklivý, zlý, nepěkná věc" 🙂

It's not weird at all, because you Rasterize the shape (for what reason?), so you convert it to a Pixel layer, and of course it can't be transformed like other vector objects - that's why the frame changes too.
 

P.S. Just a piece of advice for the future - the recording of such a large screen is quite unreadable on smaller screens (I had no chance to see what you were doing on the tablet). If you ever need help with recording, it would be more practical to make the application window smaller, rearrange the workspace, and record from the viewport.

"Učí se dobře, to nemohu říct..."

Well, I usually work with pixel layers (more often than not). The thing is that before the update, after rasterisation I was able to transform the object without any hassle. Did the update changed the behaviour in any way? 

 

Thanks a lot!

[Pšenda]

8 minutes ago, xmahlerx said:

after rasterisation

As you can see from other posts, it's not rasterization - that is, it shouldn't be, because the transformation works even after rasterization (I tried it with the latest version on Windows, hangman has it on mac).
So it looks more like a local problem for you, or if it is not the effect of a specific document.

P.S. quite often such a strange and inexplicable deviation from the standard behavior can be solved by Factory reset (holding Ctrl while starting the application). But it wants to be careful that the user doesn't delete something important.

Edited November 24, 2023 by Pšenda

[stokerg]

Hi @xmahlerx,

I've been trying to replicate this and haven't had any luck as of yet, so this doesn't appear to be related to the last update.

Could you attach the file here or upload it to our Dropbox here and I'll see if I get the same issue with the file?

[xmahlerx]

Hi everybody. Seems like updating to 2.3.0 fixed the issue for me!

Many thanks.