IPv6 Posted March 3, 2020 Posted March 3, 2020 I believe something shady is going on with masks in latest beta. Look at screenshots. I have fully-white mask with black area carved in it, added to layer. If you command-click on a mask (turning it into selection) you will get not the mask contours itself - but limited with the bounds of the parent layer! Which is definitely not needed/not useful. And even if you release mask and make selection from it again - you still get some weird bounds (of the mask itself). In previous versions, mask selection was made from all the white area inside the mask - so mask selection was bounded with document size, not the layers inside it. Since mask is totally white, except black blob in it. such unrelated bounds just ruin mask selections // * this bug is also present in [1.8.1.170]
IPv6 Posted March 5, 2020 Author Posted March 5, 2020 Still a problem in 1.8.2.173 // P.S. Also, can`t attach afphoto file, browser shows "-200" alert and nothing happens
IPv6 Posted March 19, 2020 Author Posted March 19, 2020 Sorry to bump (may seem annoying), but this is because issue really gets in the way for usual workflows and it is still not acknowledged as a problem... Problem still persist in 1.8.3.175 //
Staff MEB Posted March 19, 2020 Staff Posted March 19, 2020 No worries IPv6. Haven't checked this one nor logged it yet. IPv6 1 A Guide to Learning Affinity Software
Staff MEB Posted March 19, 2020 Staff Posted March 19, 2020 Hi IPv6, This is working exactly as in v1.7. Command-clicking the mask's thumbnail creates a selection with the same boundaries/size as the layer it's nested to. If that layer has the same size as the document (as it usually happens when you open an image) then it may look that the selection picked the whole document size. I do see how this may complicate things if the layer the mask is attached to is smaller than the document. I've logged this/passed the file to the dev team. Thanks for raising the issue. A Guide to Learning Affinity Software
Staff MEB Posted March 19, 2020 Staff Posted March 19, 2020 Hi IPv6, This should now be fixed in the next Photo Customer Beta (1.8.3). IPv6 and Andy Somerfield 2 A Guide to Learning Affinity Software
Recommended Posts