MiWe

Thanks for let me knowing. It's fixed ... Greetings

Yes, sure you're right ... I will try to be patient Greetings

Should be, but is not ... The fix for Photo solves the issue in Beta build 1.9.1.971. The latest Publisher beta shows the described behaviour. Greetings

SORRY WRONG PLACE ... PLS MOVE Can someone try to confirm the following AFPublisherbehavior, please: 1. Open a AFPublisher file which is write protected 2. Try to save it in another folder with same name or rename it, does not make any difference On my system i get a message that the file could not be written. At the destination folder a file with the correct name but size 0 byte appears. System is Windows 10, AFPublisher 1.9 release Version and Customer Beta build 1.9.1.967. This behaviour als occured in AFPhoto and has been corrected in Customer Beta build 1.9.1.971. Greetings

Nice to hear ... thanks for that information. Greetings

Hi Gabe, Images are archived as *.afphoto files on a server in read-only mode. When opening such a file, an error message appears when trying to save it to another folder/location. There is a message that the file could not be written. At the destination folder a file with the correct name but size 0 byte appears. Designer and Publisher save similar files correct. System is Windows 10, AFPhoto 1.9. Greetings

Is there any short cut to activiate the hand overlay 😁 ... Just curious. Greetings

THX for moving the topic ... Greetings

Can someone try to confirm the following AFPhoto behavior, please: 1. Open a AFPhoto file which is write protected 2. Try to save it in another folder with same name or rename it, does not make any difference On my system i get a message that the file could not be written. At the destination folder a file with the correct name but size 0 byte appears. Designer and Publisher save similar files correct. System is Windows 10, AFPhoto 1.9. Greetings

Gave it another try ... wPOINT5 works ... if you use wCOMMA5 it does not.

Scaling by a percentage of the original image does not seem to work. But you can include macros in a batch job. Maybe that could be a workaround.

Your layer named BACK has a opavity setting of 60% ... Turnining it to 100 should solve your problem. Greetings

That is what i did, disableing te live effect. As i wrote in my previous post 😉. Rasterizing would just be the alternative ... Greetings

Yes, i see ... Thanks for explanation. Played a little bit with the live filter and tried after applying to use the clone tool – no good idea. I had to disable the live effect or rasterrize the layer to work on. So both techniques have their own advantage.

Thanks, works like a charme ... But in which situation one would use tehe perspective tool? I dont see any reason for it, seems a little bit useless Greetings.