John Rostron

You are right. I applied a change from 150 to 300ppi on a document and the pixel sizes remained the same, as expected.
I then repeated the process (150 to 300) setting the units to centimetres, and the size in centimetres remained the same.
There has been problems in the past with this, but I thought that it had been fixed. I was using the new 1.7 version.
John
 

<off-topic>
Congrats to @MEB on reaching the 25k posts milestone. 
</off-topic>
 
 

A perfectly clear answer!
 

No, the BenVista PhotoZoom 7 I have is just a standalone.
John

No one disagrees with any of your frustrations with Affinity Photo's current lack of support for Adobe Photoshop's Smart Objects. We ALL wish it was there. No one is pretending it's not a problem. But it's a completely different conclusion to say, "this is what we have... let's see how we can work the problem to find a solution for the overall goal of our projects." For me personally, once I abandoned Adobe (for a wide variety of reasons), I was prepared to make adjustments — even large ones — to my workflow to accommodate a new approach. But I well understand this is undesirable and even unworkable for some.
Additionally, the issue does not seem to be that Affinity Photo is unable to understand layers; it most definitely CAN. We can open and utilize .PSD files containing any number of layers created in Photoshop. But maybe you're working with projects that present problems that some of us simply aren't experiencing. If so, PLEASE pass these on to the developers in the Feature Requests area of this forum! 
As for similar functionality to Smart Objects, here's what I'm finding (at least in simple cases): If you create an .AFPHOTO or .AFDESIGN file (or even save an Affinity Photo project as a .PSD), which you then PLACE into a new project, it shows up as a new layer with the title "Embedded File" in your new project. Using the Move tool to double-click on this embedded file reveals the various layers of that embedded document, which you can then further edit. This is similar *enough* to Smart Objects for my usage, but it most definitely doesn't go as far as it could.
EDITED TO CORRECT MY UNDERSTANDING OF HANDLING TIFF FILES: I'm still trying to understand the differences between these various placement options. For example, if I save a .TIFF file with Affinity layers intact, and then PLACE that TIFF into a new Affinity Photo project, it's placed as an "IMAGE," and double-tapping that object does NOT give access to all the layers contained therein. However, if I open that TIFF file on its own, I have access to those layers. I'm unclear as to why this is any different than a .PSD file. 

@John Rostron and @Ulysses
Are you saying there is a functionality that allows you to accomplish the same thing? It seems utterly simplistic to just look at the import problem and not the underlying lack of functionality. The fact that people are dependent on a free SaaS app for this functionality is indicative of the lack of insight and understanding. 

Affinity Photo is not able to understand layers beyond being utterly flat. Distort is a far cry. Both in terms of reliable solution (it often just doesn't map well) and the amount of time it takes to do (15 minutes best, most simplistic case, and beating your head up against it and trying to do *something* to make it work for 3-4 hours).

Mind you, this is something that consistently takes no more than 5-10 minutes in photoshop to replace. There's even a robust third party marketplace of smart object based PSDs that are amazingly simply to edit and update.

The problem clearly isn't *that* tough, or an online free SaaS app wouldn't have it solved. Shucks, affinity could buy or license the tech and make the money back in new licenses in a few months. 

Affinity products are great, but they *do* lack some highly productive workflows for some difficult problems that Adobe has solved. Pretending that these are not problems, or even more amazing, that they are solved with some inferred solution and sayings like "we do it differently" without specifics is unproductive and creates frustration that causes people to just go back to what they know can actually solve the problem.

Admitting gaps keeps people from hitting their head against an invisible ceiling they're being told doesn't exist and leaving frustrated and angry instead of coming back when the problem actually *is* solved. 

It would help others if you could post your solution so that we all could learn from your experience.
John

Looks like an image was placed over a text frame which contained a misspelled word.
Hence the squiggly red line indicating a spelling mistake, which (confusingly) shows throws the image

Very few answers about how to use the Character, Paragraph, Color, Brushes, Swatches, Assets, Transform, Snapshots, Navigator, History, etc. Studio panels are app-specific. Same for the Move, Node, View, Zoom, Art & Frame text, Pen, shapes, & several other tools. Ditto for many of the Preference panels & for features like customizing the toolbar & Tools panels or Studio layouts (floating or docked, grouped or not, etc.).
Then there are generic questions about such things as Save vs. Save As vs. Export; which file types are supported for opening, saving, or exporting; which app(s) to buy for various uses & which store to buy them from; which drawing tablets are best; how cross-platform & cross-suite compatibility works; & so on. Add to that purchase related questions about refunds, discounts, & licenses.
I could go on but I hope you get the point: basically the apps are more alike than they are different, so what applies to one very likely applies to them all.

These postings confound two aspects of Smart Objects. Affinity offers a similar workflow/functionality to that of PS smart objects, but they do not have the same structure and are thus not interchangeable. Affinity cannot read PSD smart objects, but PS may or may not be able to read the Affinity equivalent. If will all depend on whether the user needs to transfer image files between AF and PS. If not, then AF will offer all the user needs.
John

@john.rostron I think you're right. I've just compared what I see in Affinity and what I see in any other preview. Affinity shows a lot more. Thank you

Indeed :(

Many perfectly workable plugins have this "unknown" status. I would guess that the plugin does not provide Photo with some crucial bit of information that Photo is looking for. Hence the option to allow unknown plugins to work.
John

Hi Nedex,
Welcome to the forums
Affinity does come with plugins that work with Apple Photos you can find out how to use them here? https://www.youtube.com/watch?v=QdIkuUJrkCY
Thanks
Callum

I posted this question in the Photo for Windows Forum and got this reply from @Patrick Connor:
 I copied the Photo folder and renamed it Photo 1.6, then installed Photo 1.7. So far I have had no problems in running the two versions. This was only this afternoon, so there me problems surfacing at some stage, but none so far. All my plugins that worked for 1.6 are there in 1.7 and thse that I have tried work.
Note this is on Windows. It may not work on a Mac.
John
 

On my Windows box, the pixel count remains the same, but it doesn't on yours. I suggest that you submit it as a bug report.
John

It shouldn't but it is. Look at the top left of the Affinity screenshots. Its just adding pixels, even the file size goes up. Surely the print size i.e. 10cm should come down if the resolution is upped?

Yes. In my eagerness to upgrade I went and purchased a new copy of 1.7 Doh!
 

Thanks for the link carl. Has Trump solved the Brexit problem for England yet?  LOL

Yes. Set up a Batch job. (search photo help "batch job" for a more in-depth explanation).

From the help....
"About batch jobs
The Batch Job feature allows you to specify an unrestricted number of source files to process and export.......both the exported file format and image dimensions are configurable."

Thanks, Patrick. I think that I shall try copying the folder and seeing if the .exe file works before installing 1.7. I would probably not be trying to apply plugins to an .afphoto file, but to newly acquired .awr or .jpg files.
John

I can confirm that the new NikCollection V 2 works with no problem together with AP 1.7. Just bought Nik V2 today.

If you're trying to delete all the text, do as John suggested just above your post.
If you're trying to delete part of the text, you may have trouble as it is not text, but an image of text.
Can you provide more information on exactly what you want to do to that block of text? It may be better to delete the complete block (using John's instructions) and completely recreate that block of text by providing a rectangle of an appropriate color as a background, and using the Frame Text Tool to completely redo the text, keeping just what you want, and putting it on top of the colored rectangle.

All one paragraph. I’m designing a phone APP where a long text is divided by chapters and I need to repeat that operation many times

Please can we not have a thirty-page thread on this!
John