CyberAngel

I believe I am all good, I just do not know how or why the linked images where broken as they never moved.

It happens with all version 2 installations, and yes after I posted this I went back through the comments and managed to see the DDU part. And that worked. However, not fully. As I was able to eventually open it, after a day or two of testing things. For me, it boiled down to external links being broken. I had managed to get to a point where I could at least create a new document, but certain projects I could not open. When I eventually got one opened as I mentioned it was to actually do with external links could not be found or something. Once I relinked these or replaced them, the document was able to be opened again. So in summary, the DDU managed to get me to be able to create a document, but it did still fail as described above.

I am also getting this same exact issue And creating new documents also crashes Photo. I do not have any issues with Designer or Publisher. I have tried Uninstalling, Photo 2.2.1 and reinstalling 2.00 and upgrade each version one at a time. I also have Photo 1.0 installed and it is also having the same issue. There is nothing in the Event Viewer, I have deleted or cleared it and opened Photo a number of times, and nothing is added to the events here. Is there something more I can provide? Log.txt 0acd1e6d-a377-4db4-bee7-388210b07cf9.dmp

Thanks, I don't use the photo stuff enough to remember it.

Remind me why rasterizing this placed image is needed here?

And you were told a number of times, we should not have to do this. It is now confirmed by the developers as unwanted behaviour and is on their radar to be fixed, that is all that concerns me now.

Yet, we can agree that is how it is working. What we disagree on here, is how it should work. You say it is a pixel selection, I say it should not be anything till you take action on it!

Exactly.

No idea, I am still learning the suite of tools. I can only say what I have expected to happen, coming from the usage of other programs. And why I believe this is an issue. While I accept there are work arounds, they are all in my opinion long winded unnecessary steps to something that appears to be broken.

That video does nothing for almost half of it, but what does it have to do with the marquee tool!

Right, and I have said that the expectation is that we should be able to resize the Marquee without it doing what it is doing. I frankly do not care what it is doing now, only what the expectation of how everything else works. In that I mean I can use the transform to resize everything without affecting what is underneath, yet the marquee seems to be different. That is all that matters here.

Well, the really confusing part in all this, is when feathering is set to zero. One has to ask why any feathering is occurring in the first place, and why add an extra 1 or 2 pixels no matter how much it is resized.

But it doesn't at least not for me!

I was trying to understand what Brian was saying!

Which is all good, but the expectation would be that this doesn't happen until the Ctrl+C has occurred.

If that was true, would making the marquee 10x10 and then making it 224x248 via the transform make it extremely stretched or something?

Thanks for the information Sean, looking forward to seeing it implemented.

And so does it when it is coded correctly in the first place.

And I have said a number of times, that I should not have to do something like this!

Hopefully, the main interest is the extra pixel and feathering.

And what I said, is that if the layer is selected I get the same results. Secondly, I am using it without doing much here, so if the layer is being deselected I would question why, as it is the only layer there.

It doesn't matter if the layer is highlighted or not, the results are the same!

This is on Windows 11, I will attach a link that has the files necessary and a video explaining the issues. The problem is that as a new user, I have come accustomed to selecting something, changing that selection via resize handles, and/or manipulating its position and size. Which in Affinity Photo's case causes unexpected results, in some cases 3 different results. I have also made a suggestion, that the marquee tool can be manipulated via handles, an example of this would be like this I have attached the link below to the uploaded file to show what I am doing and the different results that I get.

Right, which is what I have suspected. And why I was not interested in work arounds, or it is because it does this, or it does that. I was interested in knowing if what I am seeing is indeed a bug.

Ok, so because I feel that nobody has fully understand what I am talking about, I have put together a video. Before watching this, please take a moment to reread the title of this post, which clearly says that using the marquee tool for copy and paste is not consistent! This video has proven that I can duplicate 2 of the 3 issues I have experienced, this post has shown the other via an image. AffinitySelectionIssue.mp4