John Rostron

Look at Dave Straker's 'notes' for V1. This will covera most of what is found in V2.
 
John

Look at Dave Straker's 'notes' for V1. This will covera most of what is found in V2.
 
John

Look at Dave Straker's 'notes' for V1. This will covera most of what is found in V2.
 
John

I think that @mthorneris saying the same thing as @imagodespira : some V1 files cannot be opened in V2. @walt.farrell's reply addresses he problem that V2 files cannot be opened in V1.
John

As I read it, imagodespira said that they didn’t know why V1 files couldn’t be opened (I’m assuming in V2), which is a different thing, as far as I can see, to what mthorner said which was about opening V2 documents in the V1 applications.
My reply was to the assertion “it is not possible to open V1 files” which, if I read it correctly, was false (except for certain bugs/issues which aren’t part of expected working).
There may be two different issues at work here which could be causing some confusion.

HI John I tried in that way but always affect to the quality with a small size, thank you

Hello @sammybeeand welcome to the forums.
The choice of file type now appears in a drop-down list right at the top of the Export dialogue.
John

See my reply above:
John

Hello @sammybeeand welcome to the forums.
The choice of file type now appears in a drop-down list right at the top of the Export dialogue.
John

Hi
Here is a simple automn leave treated with Affinity Photo
 
More to see at : kbfotoart.com

True. But even if File > Place worked (as it did in V1), it has the same effect. It would Place whatever you Placed during the recording of the macro. It would not give you a choice during playback.

Please fix it so Affinity does not save filename.tif.tiff files. It breaks rountriping in Lightroom and it's so frustrating. Please adopt the ability to just save .TIF files without the extra F. 
 
THANKS

I have put together a set of macros to change the dpi of an image without changing the pixel dimensions. The set comprises macros to change the dpi to 72, 96, 144, 150, 180, 192, 300 and 400dpi.
These macros were recorded in Photo 1.6 because there were reports that similar macros recorded in 1.7 would always resample, even if the Resample box was unticked. I have checked that these macros work in 1.8, which they do. I also note that in 1.8 the Resize function will change the dpi without resampling.
Here is the Library file: Change DPI 1.6.afmacros
Thanks to @carl123 for setting the ball rolling with his macro here.
EDIT: This macro library has been recreated (in 1.6) and re-imported into this message.
EDIT: I have now re-recorded them in Photo 1.10, but they still do not work!
John

Hello @ibericjack, and welcome to the forum.
This forum focusses on Affinity Software. Your problem seems to be hardware related and not really relevant to this forum.
The only thing I could suggest is that you find someone with a suitable printer (not necessarily the same make/model that you have, but with similar abilities)  and send them your affinity document for printing. Do you have a local print shop you could use? Take your document there on a memory stick. Note that not everyone can read Affinity-format documents so you would need to export as (probably) pdf.
John

Is it perhaps overridden? Is it a [No Style] Paragraph Style or a Heading that I made myself Paragraph Style?
You have to check the Text Frame, the Document and the Paragraph Style. Plus check the Text Style's panel's name for the Heading that I made myself and see if there are any overrides. Note that I have not uncheck the Text Style Baseline, it still has the Inherit mark, an oversight on my part.

@John Rostron Am I correct in assuming that you do not want to use the baseline grid anywhere in the document?
If you have disabled the baseline grid in View > Baseline Grid, I don't believe the baseline grid options in other areas could be causing the "jumpy text" issue. For example, enabling the baseline grid in the Text Frame panel won't make the text jump around when the text frame is moved, because the baseline is anchored to the text frame.
If you could upload a Publisher file with a text frame exhibiting the behavior, someone in here should be able to figure out what's going on. 

Yes, I understand a baseline grid can be set in a text frame. But if the text frame with 'Use Baseline Grid' enabled is moved vertically, the text doesn't display the behavior the OP described, because the baseline moves with the text frame.
That's why I figured the Text Frame baseline grid options may not play a role in the issue. But, could be I'm not understanding the issue completely.

Also make sure that Use Independent Baseline Grid is disabled in the Text Frame panel

Also worth making sure that Ignore Baseline Grid is ticked in the General tab of the Text Frame Panel:

Screen Recording 2022-11-28 at 20.42.35.mov    
 
 
I'm pretty certain it's something to do with the baseline grid, but there are a lot of different options to work through.

They are talking about tethered photography, programs like Hasselblad's Phocus etc.
 
 

The only thing I can think of is they mean: take a picture and have it wirelessly appear in AP. Some cameras/phones will upload directly to iCloud for example.
So far as I know, AP does not 'listen' for incoming files.

Your second screen shot doesn't show the complete Spacing Panel so it's a bit hard to tell what's going on.
I can replicate your 'small' 20pt text in a couple of ways: either by setting it to Subscript in the Positioning & Transform section of the Character Panel, or by reducing the Horizontal and Vertical Scale in the same place. 
 

 
(The scaling options are just above the Subscript button.) Might be worth checking those out.

I found the answer: 
"
If you have a .afmacro (no s) file you import it using the Macro panel. If you have a .afmacros file you import it using the Library panel." The macros have an s on the end. They imported fine in the library panel, and they work perfectly.
Thank you!

Thanks! That explains why those functions can't work very clearly! 

As far as I am aware, the Affinity plugin interface accepts a single image, and returns a single image of the same size. PhotoZoom, by design, will return an image of a different size. I cannot see this being rectified until Affinity changes its plugin API. In the meantime, do like I do, use the standalone.
John