Hangman

This appears to be specific to a right-facing page document...
It works with a multi-page left-facing page document and with a multi-page non-facing page document, just not with a multi-page right-facing page document, though you can still edit the pressure map with a multi-page, right-facing document, you just can't edit the line width on the page by selecting 'points' on the object itself...

For anyone who may be interested, in addition to the options provided with the initial post for the new QR Code creation tool here are a few additions that work with iOS...
Syntax Provided in the Initial Post for QR Code Creation in Affinity 2.5 Beta Apps
SMS
Payload structure: SMSTO:number:text message
Eg. SMSTO:07513123456:Hello mate!
GEO location
Payload structure: GEO:lat:lon:height
Eg. GEO:40.71872,-73.98905,100
WIFI credentials
Payload structure: WIFI:S:ssid;T:type;P:password;;
Eg. WIFI:S:MyWiFiSSID;T:WPA;P:MyPassW0rd;;
 
Note: I've not tested these on Android but I'd be keen to know which work (with the applicable options) and which don't if anyone is happy to test...
Additional Syntax Options for QR Code Creation in the Affinity 2.5 Beta Apps
Phone
Payload structure: TEL:number
e.g., TEL:07772123456

Email
Payload structure: MAILTO:email address
e.g., MAILTO:jon.doe@example.com

Email Additions (Cc, Bcc, Subject, Message)
Payload structure: MAILTO:email address?CC=email address&BCC=email address&SUBJECT=subject&BODY=message
e.g., MAILTO:john.smith@example.com?CC=john.doe@example.com&BCC=jane.doe@example.com&SUBJECT=Friday Drinks&BODY=We are all meeting at the Dog & Duck on Friday after work, hope you can make it.
FaceTime
Payload structure: FACETIME:mobile number
e.g., FACETIME:07772123456
YouTube
Payload structure: URL:https://youtubeurl
e.g., https://www.youtube.com/AffinitySuite
WhatsApp
Payload structure: URL:https://wa.me/internationalnumber?text=message
e.g., https://wa.me/447772123456?text=We are all meeting at the Dog & Duck on Friday after work, hope you can make it.
Note 1: The mobile number needs to include the international dialling code without any prefixed zeros, e.g., UK 44 and US 1 as opposed to 0044 or 01.
Note 2: Reserved characters need to use URL encoding when included as part of the message, i.e., ‘Dog & Duck’ should be typed as ‘Dog %26 Duck’ otherwise the message element is truncated at ‘Dog’.
Examples of Reserved Characters

Spotify Track
Payload structure: https://open.spotify.com/track/songlink
e.g., https://open.spotify.com/track/3Z5VaAEN7NWkgBXbCXNilW?si=91dfd85f75df4009
Spotify Playlist
Payload structure: https://open.spotify.com/playlist/playlistlink
e.g., https://open.spotify.com/playlist/7y40TSg305MTZ3n3Q2LqSF?si=dc0c24f1a6a34cdd
Address Book Contact (vCard)
Payload structure:
BEGIN:VCARD
VERSION:3.0
PRODID:-//Apple Inc.//macOS 12.7.4//EN
N:LasteName;FirstName;;;
FN:FirstName LasteName
ORG:Company;
EMAIL;type=INTERNET;type=WORK;type=pref:name@company.com
TEL;type=WORK;type=VOICE;type=pref:Work Number
TEL;type=CELL;type=VOICE:Mobile Number
ADR;type=HOME;type=pref:;;Address
NOTE:Notes
item1.URL;type=pref:Web Address
item1.X-ABLabel:_$!<HomePage>!$_
BDAY:2000-02-28
END:VCARD
While the QR Code generator library (used in the v2.5 Beta for QR Code creation) supports the vCard (.vcf) format, currently Affinity apps don’t because of the requirement to use a CRLF (Carriage Return/Linefeed) after each line entry which the single-line Payload format used for QR Code creation in the Affinity apps don't accept and means the vCard formats fails with a No Usable Data Found error message.
The alternative for Contact QR Codes is to use the more limited MECARD format which is accepted by the Affinity apps when creating a new Contact QR Code…
Address Book Contact (MECARD)
Payload structure: MECARD:N:Last Name,First Name;ADR:Address;TEL:number;TEL:number;EMAIL:emailaddress;NOTE:note
e.g., MECARD:N:Cook,Tim;ADR:One Apple Park Way, Cupertino, CA 95014, United States;TEL:+14089961010;TEL:+17513123456;EMAIL:tim.cook@apple.com;URL:https://apple.com;BDAY:19600111;NOTE:”Apple Vision Pro, You navigate simply by using your eyes, hands, and voice.”;;

PDF File
Payload structure: https://hostlurl/file/pdflink
e.g., https://drive.google.com/file/d/1WZD6wOgG1bkPQfcNA_MMCIuPhKVhWWQf/view?usp=sharing

Add to Calendar Event for Apple and Google Calendar (.ics)
Payload structure:
BEGIN:VCALENDAR
VERSION:2.0
PRODID:Spatie calendar-links
BEGIN:VEVENT
UID:90bbafd033c512f7590d844a0d65b449
SUMMARY:Run the London Marathon
DTSTAMP:20240421T080000Z
DTSTART:20240421T080000Z
DTEND:20240421T130000Z
DESCRIPTION:I'm running the London Marathon
LOCATION:London
END:VEVENT
END:VCALENDAR
While the QR Code generator library (used in the v2.5 Beta for QR Code creation) supports both the VCALENDAR AND VEVENT formats, currently Affinity apps don’t because of the requirement to use a CRLF (Carriage Return/Linefeed) after each line entry which the single-line Payload format used for QR Code creation in the Affinity apps don't accept and means the VCALENDAR AND VEVENT formats fail with a No Usable Data Found error message.

Thanks for the insight, Hangman! 
I'd prefer manual control over those settings though.

Hi @baoyu,
Based on a great deal of testing it looks as though these are both applied automatically based on the complexity of the QR Code... e.g., when the data bits reach their maximum, i.e., 3Kb, the file created is a 'Version 40 QR Code' with an 'Error Correction' Level of "L" vs a simple QR Code with 52 bits of data which creates a 'Version 1 QR Code' with an 'Error Correction' Level of "H"...
Version 40 - Error Correction Level of L (Left) | Version 1 - Error Correction Level of H (Right)

I'm proposing this as a bug because while the QR Code generator library (used in the v2.5 Beta for QR Code creation) supports the vCard (.vcf), VCALENDAR and VEVENT (.ics) formats it's not possible to create QR Codes with the Affinity apps using either format since both require a CRLF (Carriage Return/Linefeed) after each line entry which the single-line Payload format used for QR Code creation in the Affinity apps don't accept and means the following formats fail:
\n = LF (Line Feed) → Used as a new line character in Unix/Mac OS X \\n = An escaped LF (Line Feed) → Used as a new line character in Unix/Mac OS X \r = CR (Carriage Return) → Used as a new line character in Mac OS before Mac OS X \r\n = CR + LF → Used as a new line character on Windows %0a = a URL encoded (Line Feed) → Used as a line feed character on Unix/Mac OS X %0d = a URL encoded (Carriage Return) → Used as a carriage return character on Unix/Mac OS X %0d%0a = a URL encoded (Carriage Return/Line Feed) → Used as a carriage return/line feed character on Unix/Mac OS X %0d%0a%0d%0a = a URL encoded form of CRLFCRLF → which tricks the server into inserting a CRLF sequence on Unix/Mac OS X This means that while it is possible to create a vCard QR Code with the QR Code generator library using this format:
BEGIN:VCARD
VERSION:3.0
PRODID:-//Apple Inc.//macOS 12.7.4//EN
N:LasteName;FirstName;;;
FN:FirstName LasteName
ORG:Company;
EMAIL;type=INTERNET;type=WORK;type=pref:name@company.com
TEL;type=WORK;type=VOICE;type=pref:Work Number
TEL;type=CELL;type=VOICE:Mobile Number
ADR;type=HOME;type=pref:;;Address
NOTE:Notes
item1.URL;type=pref:Web Address
item1.X-ABLabel:_$!<HomePage>!$_
BDAY:2000-02-28
END:VCARD
or an 'Add to Calendar' VEVENT QR Code with the QR Code generator library using this format:
BEGIN:VCALENDAR
VERSION:2.0
PRODID:Spatie calendar-links
BEGIN:VEVENT
UID:90bbafd033c512f7590d844a0d65b449
SUMMARY:Run the London Marathon
DTSTAMP:20240421T080000Z
DTSTART:20240421T080000Z
DTEND:20240421T130000Z
DESCRIPTION:I'm running the London Marathon
LOCATION:London
END:VEVENT
END:VCALENDAR
it's not possible to create a QR Code using the Affinity apps because of the single-line format which results in a No Usable Data Found error message when scanning the generated QR Code using the iPhone camera's built-in QR Code Scanner...
Note: I've not tested this on Android but my assumption is that this will result in the same issue...

That's what a long day of testing does to one's ability to spell 'Quiet' (or anything) correctly...
Post amended accordingly...

Spell check won’t save you!

 

Feature Request for QR Code Creation...
The QR Code generator library (used in the v2.5 Beta for QR Code creation) supports Quiet Zone Border Modules.
It would be great if an option could be added to both the Create QR Code tool and the context toolbar so a Quiet Zone Border Module value could be specified whether using either a Module value or a value based on the currently selected Affinity UOM...
It's a bit of a pain having to manually add a Quiet Zone Border to a QR Code so the proposal is this... 

 

For anyone who may be interested, in addition to the options provided with the initial post for the new QR Code creation tool here are a few additions that work with iOS...
Syntax Provided in the Initial Post for QR Code Creation in Affinity 2.5 Beta Apps
SMS
Payload structure: SMSTO:number:text message
Eg. SMSTO:07513123456:Hello mate!
GEO location
Payload structure: GEO:lat:lon:height
Eg. GEO:40.71872,-73.98905,100
WIFI credentials
Payload structure: WIFI:S:ssid;T:type;P:password;;
Eg. WIFI:S:MyWiFiSSID;T:WPA;P:MyPassW0rd;;
 
Note: I've not tested these on Android but I'd be keen to know which work (with the applicable options) and which don't if anyone is happy to test...
Additional Syntax Options for QR Code Creation in the Affinity 2.5 Beta Apps
Phone
Payload structure: TEL:number
e.g., TEL:07772123456

Email
Payload structure: MAILTO:email address
e.g., MAILTO:jon.doe@example.com

Email Additions (Cc, Bcc, Subject, Message)
Payload structure: MAILTO:email address?CC=email address&BCC=email address&SUBJECT=subject&BODY=message
e.g., MAILTO:john.smith@example.com?CC=john.doe@example.com&BCC=jane.doe@example.com&SUBJECT=Friday Drinks&BODY=We are all meeting at the Dog & Duck on Friday after work, hope you can make it.
FaceTime
Payload structure: FACETIME:mobile number
e.g., FACETIME:07772123456
YouTube
Payload structure: URL:https://youtubeurl
e.g., https://www.youtube.com/AffinitySuite
WhatsApp
Payload structure: URL:https://wa.me/internationalnumber?text=message
e.g., https://wa.me/447772123456?text=We are all meeting at the Dog & Duck on Friday after work, hope you can make it.
Note 1: The mobile number needs to include the international dialling code without any prefixed zeros, e.g., UK 44 and US 1 as opposed to 0044 or 01.
Note 2: Reserved characters need to use URL encoding when included as part of the message, i.e., ‘Dog & Duck’ should be typed as ‘Dog %26 Duck’ otherwise the message element is truncated at ‘Dog’.
Examples of Reserved Characters

Spotify Track
Payload structure: https://open.spotify.com/track/songlink
e.g., https://open.spotify.com/track/3Z5VaAEN7NWkgBXbCXNilW?si=91dfd85f75df4009
Spotify Playlist
Payload structure: https://open.spotify.com/playlist/playlistlink
e.g., https://open.spotify.com/playlist/7y40TSg305MTZ3n3Q2LqSF?si=dc0c24f1a6a34cdd
Address Book Contact (vCard)
Payload structure:
BEGIN:VCARD
VERSION:3.0
PRODID:-//Apple Inc.//macOS 12.7.4//EN
N:LasteName;FirstName;;;
FN:FirstName LasteName
ORG:Company;
EMAIL;type=INTERNET;type=WORK;type=pref:name@company.com
TEL;type=WORK;type=VOICE;type=pref:Work Number
TEL;type=CELL;type=VOICE:Mobile Number
ADR;type=HOME;type=pref:;;Address
NOTE:Notes
item1.URL;type=pref:Web Address
item1.X-ABLabel:_$!<HomePage>!$_
BDAY:2000-02-28
END:VCARD
While the QR Code generator library (used in the v2.5 Beta for QR Code creation) supports the vCard (.vcf) format, currently Affinity apps don’t because of the requirement to use a CRLF (Carriage Return/Linefeed) after each line entry which the single-line Payload format used for QR Code creation in the Affinity apps don't accept and means the vCard formats fails with a No Usable Data Found error message.
The alternative for Contact QR Codes is to use the more limited MECARD format which is accepted by the Affinity apps when creating a new Contact QR Code…
Address Book Contact (MECARD)
Payload structure: MECARD:N:Last Name,First Name;ADR:Address;TEL:number;TEL:number;EMAIL:emailaddress;NOTE:note
e.g., MECARD:N:Cook,Tim;ADR:One Apple Park Way, Cupertino, CA 95014, United States;TEL:+14089961010;TEL:+17513123456;EMAIL:tim.cook@apple.com;URL:https://apple.com;BDAY:19600111;NOTE:”Apple Vision Pro, You navigate simply by using your eyes, hands, and voice.”;;

PDF File
Payload structure: https://hostlurl/file/pdflink
e.g., https://drive.google.com/file/d/1WZD6wOgG1bkPQfcNA_MMCIuPhKVhWWQf/view?usp=sharing

Add to Calendar Event for Apple and Google Calendar (.ics)
Payload structure:
BEGIN:VCALENDAR
VERSION:2.0
PRODID:Spatie calendar-links
BEGIN:VEVENT
UID:90bbafd033c512f7590d844a0d65b449
SUMMARY:Run the London Marathon
DTSTAMP:20240421T080000Z
DTSTART:20240421T080000Z
DTEND:20240421T130000Z
DESCRIPTION:I'm running the London Marathon
LOCATION:London
END:VEVENT
END:VCALENDAR
While the QR Code generator library (used in the v2.5 Beta for QR Code creation) supports both the VCALENDAR AND VEVENT formats, currently Affinity apps don’t because of the requirement to use a CRLF (Carriage Return/Linefeed) after each line entry which the single-line Payload format used for QR Code creation in the Affinity apps don't accept and means the VCALENDAR AND VEVENT formats fail with a No Usable Data Found error message.

For anyone who may be interested, in addition to the options provided with the initial post for the new QR Code creation tool here are a few additions that work with iOS...
Syntax Provided in the Initial Post for QR Code Creation in Affinity 2.5 Beta Apps
SMS
Payload structure: SMSTO:number:text message
Eg. SMSTO:07513123456:Hello mate!
GEO location
Payload structure: GEO:lat:lon:height
Eg. GEO:40.71872,-73.98905,100
WIFI credentials
Payload structure: WIFI:S:ssid;T:type;P:password;;
Eg. WIFI:S:MyWiFiSSID;T:WPA;P:MyPassW0rd;;
 
Note: I've not tested these on Android but I'd be keen to know which work (with the applicable options) and which don't if anyone is happy to test...
Additional Syntax Options for QR Code Creation in the Affinity 2.5 Beta Apps
Phone
Payload structure: TEL:number
e.g., TEL:07772123456

Email
Payload structure: MAILTO:email address
e.g., MAILTO:jon.doe@example.com

Email Additions (Cc, Bcc, Subject, Message)
Payload structure: MAILTO:email address?CC=email address&BCC=email address&SUBJECT=subject&BODY=message
e.g., MAILTO:john.smith@example.com?CC=john.doe@example.com&BCC=jane.doe@example.com&SUBJECT=Friday Drinks&BODY=We are all meeting at the Dog & Duck on Friday after work, hope you can make it.
FaceTime
Payload structure: FACETIME:mobile number
e.g., FACETIME:07772123456
YouTube
Payload structure: URL:https://youtubeurl
e.g., https://www.youtube.com/AffinitySuite
WhatsApp
Payload structure: URL:https://wa.me/internationalnumber?text=message
e.g., https://wa.me/447772123456?text=We are all meeting at the Dog & Duck on Friday after work, hope you can make it.
Note 1: The mobile number needs to include the international dialling code without any prefixed zeros, e.g., UK 44 and US 1 as opposed to 0044 or 01.
Note 2: Reserved characters need to use URL encoding when included as part of the message, i.e., ‘Dog & Duck’ should be typed as ‘Dog %26 Duck’ otherwise the message element is truncated at ‘Dog’.
Examples of Reserved Characters

Spotify Track
Payload structure: https://open.spotify.com/track/songlink
e.g., https://open.spotify.com/track/3Z5VaAEN7NWkgBXbCXNilW?si=91dfd85f75df4009
Spotify Playlist
Payload structure: https://open.spotify.com/playlist/playlistlink
e.g., https://open.spotify.com/playlist/7y40TSg305MTZ3n3Q2LqSF?si=dc0c24f1a6a34cdd
Address Book Contact (vCard)
Payload structure:
BEGIN:VCARD
VERSION:3.0
PRODID:-//Apple Inc.//macOS 12.7.4//EN
N:LasteName;FirstName;;;
FN:FirstName LasteName
ORG:Company;
EMAIL;type=INTERNET;type=WORK;type=pref:name@company.com
TEL;type=WORK;type=VOICE;type=pref:Work Number
TEL;type=CELL;type=VOICE:Mobile Number
ADR;type=HOME;type=pref:;;Address
NOTE:Notes
item1.URL;type=pref:Web Address
item1.X-ABLabel:_$!<HomePage>!$_
BDAY:2000-02-28
END:VCARD
While the QR Code generator library (used in the v2.5 Beta for QR Code creation) supports the vCard (.vcf) format, currently Affinity apps don’t because of the requirement to use a CRLF (Carriage Return/Linefeed) after each line entry which the single-line Payload format used for QR Code creation in the Affinity apps don't accept and means the vCard formats fails with a No Usable Data Found error message.
The alternative for Contact QR Codes is to use the more limited MECARD format which is accepted by the Affinity apps when creating a new Contact QR Code…
Address Book Contact (MECARD)
Payload structure: MECARD:N:Last Name,First Name;ADR:Address;TEL:number;TEL:number;EMAIL:emailaddress;NOTE:note
e.g., MECARD:N:Cook,Tim;ADR:One Apple Park Way, Cupertino, CA 95014, United States;TEL:+14089961010;TEL:+17513123456;EMAIL:tim.cook@apple.com;URL:https://apple.com;BDAY:19600111;NOTE:”Apple Vision Pro, You navigate simply by using your eyes, hands, and voice.”;;

PDF File
Payload structure: https://hostlurl/file/pdflink
e.g., https://drive.google.com/file/d/1WZD6wOgG1bkPQfcNA_MMCIuPhKVhWWQf/view?usp=sharing

Add to Calendar Event for Apple and Google Calendar (.ics)
Payload structure:
BEGIN:VCALENDAR
VERSION:2.0
PRODID:Spatie calendar-links
BEGIN:VEVENT
UID:90bbafd033c512f7590d844a0d65b449
SUMMARY:Run the London Marathon
DTSTAMP:20240421T080000Z
DTSTART:20240421T080000Z
DTEND:20240421T130000Z
DESCRIPTION:I'm running the London Marathon
LOCATION:London
END:VEVENT
END:VCALENDAR
While the QR Code generator library (used in the v2.5 Beta for QR Code creation) supports both the VCALENDAR AND VEVENT formats, currently Affinity apps don’t because of the requirement to use a CRLF (Carriage Return/Linefeed) after each line entry which the single-line Payload format used for QR Code creation in the Affinity apps don't accept and means the VCALENDAR AND VEVENT formats fail with a No Usable Data Found error message.

Feature Request for QR Code Creation...
The QR Code generator library (used in the v2.5 Beta for QR Code creation) supports Quiet Zone Border Modules.
It would be great if an option could be added to both the Create QR Code tool and the context toolbar so a Quiet Zone Border Module value could be specified whether using either a Module value or a value based on the currently selected Affinity UOM...
It's a bit of a pain having to manually add a Quiet Zone Border to a QR Code so the proposal is this... 

 

For anyone who may be interested, in addition to the options provided with the initial post for the new QR Code creation tool here are a few additions that work with iOS...
Syntax Provided in the Initial Post for QR Code Creation in Affinity 2.5 Beta Apps
SMS
Payload structure: SMSTO:number:text message
Eg. SMSTO:07513123456:Hello mate!
GEO location
Payload structure: GEO:lat:lon:height
Eg. GEO:40.71872,-73.98905,100
WIFI credentials
Payload structure: WIFI:S:ssid;T:type;P:password;;
Eg. WIFI:S:MyWiFiSSID;T:WPA;P:MyPassW0rd;;
 
Note: I've not tested these on Android but I'd be keen to know which work (with the applicable options) and which don't if anyone is happy to test...
Additional Syntax Options for QR Code Creation in the Affinity 2.5 Beta Apps
Phone
Payload structure: TEL:number
e.g., TEL:07772123456

Email
Payload structure: MAILTO:email address
e.g., MAILTO:jon.doe@example.com

Email Additions (Cc, Bcc, Subject, Message)
Payload structure: MAILTO:email address?CC=email address&BCC=email address&SUBJECT=subject&BODY=message
e.g., MAILTO:john.smith@example.com?CC=john.doe@example.com&BCC=jane.doe@example.com&SUBJECT=Friday Drinks&BODY=We are all meeting at the Dog & Duck on Friday after work, hope you can make it.
FaceTime
Payload structure: FACETIME:mobile number
e.g., FACETIME:07772123456
YouTube
Payload structure: URL:https://youtubeurl
e.g., https://www.youtube.com/AffinitySuite
WhatsApp
Payload structure: URL:https://wa.me/internationalnumber?text=message
e.g., https://wa.me/447772123456?text=We are all meeting at the Dog & Duck on Friday after work, hope you can make it.
Note 1: The mobile number needs to include the international dialling code without any prefixed zeros, e.g., UK 44 and US 1 as opposed to 0044 or 01.
Note 2: Reserved characters need to use URL encoding when included as part of the message, i.e., ‘Dog & Duck’ should be typed as ‘Dog %26 Duck’ otherwise the message element is truncated at ‘Dog’.
Examples of Reserved Characters

Spotify Track
Payload structure: https://open.spotify.com/track/songlink
e.g., https://open.spotify.com/track/3Z5VaAEN7NWkgBXbCXNilW?si=91dfd85f75df4009
Spotify Playlist
Payload structure: https://open.spotify.com/playlist/playlistlink
e.g., https://open.spotify.com/playlist/7y40TSg305MTZ3n3Q2LqSF?si=dc0c24f1a6a34cdd
Address Book Contact (vCard)
Payload structure:
BEGIN:VCARD
VERSION:3.0
PRODID:-//Apple Inc.//macOS 12.7.4//EN
N:LasteName;FirstName;;;
FN:FirstName LasteName
ORG:Company;
EMAIL;type=INTERNET;type=WORK;type=pref:name@company.com
TEL;type=WORK;type=VOICE;type=pref:Work Number
TEL;type=CELL;type=VOICE:Mobile Number
ADR;type=HOME;type=pref:;;Address
NOTE:Notes
item1.URL;type=pref:Web Address
item1.X-ABLabel:_$!<HomePage>!$_
BDAY:2000-02-28
END:VCARD
While the QR Code generator library (used in the v2.5 Beta for QR Code creation) supports the vCard (.vcf) format, currently Affinity apps don’t because of the requirement to use a CRLF (Carriage Return/Linefeed) after each line entry which the single-line Payload format used for QR Code creation in the Affinity apps don't accept and means the vCard formats fails with a No Usable Data Found error message.
The alternative for Contact QR Codes is to use the more limited MECARD format which is accepted by the Affinity apps when creating a new Contact QR Code…
Address Book Contact (MECARD)
Payload structure: MECARD:N:Last Name,First Name;ADR:Address;TEL:number;TEL:number;EMAIL:emailaddress;NOTE:note
e.g., MECARD:N:Cook,Tim;ADR:One Apple Park Way, Cupertino, CA 95014, United States;TEL:+14089961010;TEL:+17513123456;EMAIL:tim.cook@apple.com;URL:https://apple.com;BDAY:19600111;NOTE:”Apple Vision Pro, You navigate simply by using your eyes, hands, and voice.”;;

PDF File
Payload structure: https://hostlurl/file/pdflink
e.g., https://drive.google.com/file/d/1WZD6wOgG1bkPQfcNA_MMCIuPhKVhWWQf/view?usp=sharing

Add to Calendar Event for Apple and Google Calendar (.ics)
Payload structure:
BEGIN:VCALENDAR
VERSION:2.0
PRODID:Spatie calendar-links
BEGIN:VEVENT
UID:90bbafd033c512f7590d844a0d65b449
SUMMARY:Run the London Marathon
DTSTAMP:20240421T080000Z
DTSTART:20240421T080000Z
DTEND:20240421T130000Z
DESCRIPTION:I'm running the London Marathon
LOCATION:London
END:VEVENT
END:VCALENDAR
While the QR Code generator library (used in the v2.5 Beta for QR Code creation) supports both the VCALENDAR AND VEVENT formats, currently Affinity apps don’t because of the requirement to use a CRLF (Carriage Return/Linefeed) after each line entry which the single-line Payload format used for QR Code creation in the Affinity apps don't accept and means the VCALENDAR AND VEVENT formats fail with a No Usable Data Found error message.

I'm proposing this as a bug because while the QR Code generator library (used in the v2.5 Beta for QR Code creation) supports the vCard (.vcf), VCALENDAR and VEVENT (.ics) formats it's not possible to create QR Codes with the Affinity apps using either format since both require a CRLF (Carriage Return/Linefeed) after each line entry which the single-line Payload format used for QR Code creation in the Affinity apps don't accept and means the following formats fail:
\n = LF (Line Feed) → Used as a new line character in Unix/Mac OS X \\n = An escaped LF (Line Feed) → Used as a new line character in Unix/Mac OS X \r = CR (Carriage Return) → Used as a new line character in Mac OS before Mac OS X \r\n = CR + LF → Used as a new line character on Windows %0a = a URL encoded (Line Feed) → Used as a line feed character on Unix/Mac OS X %0d = a URL encoded (Carriage Return) → Used as a carriage return character on Unix/Mac OS X %0d%0a = a URL encoded (Carriage Return/Line Feed) → Used as a carriage return/line feed character on Unix/Mac OS X %0d%0a%0d%0a = a URL encoded form of CRLFCRLF → which tricks the server into inserting a CRLF sequence on Unix/Mac OS X This means that while it is possible to create a vCard QR Code with the QR Code generator library using this format:
BEGIN:VCARD
VERSION:3.0
PRODID:-//Apple Inc.//macOS 12.7.4//EN
N:LasteName;FirstName;;;
FN:FirstName LasteName
ORG:Company;
EMAIL;type=INTERNET;type=WORK;type=pref:name@company.com
TEL;type=WORK;type=VOICE;type=pref:Work Number
TEL;type=CELL;type=VOICE:Mobile Number
ADR;type=HOME;type=pref:;;Address
NOTE:Notes
item1.URL;type=pref:Web Address
item1.X-ABLabel:_$!<HomePage>!$_
BDAY:2000-02-28
END:VCARD
or an 'Add to Calendar' VEVENT QR Code with the QR Code generator library using this format:
BEGIN:VCALENDAR
VERSION:2.0
PRODID:Spatie calendar-links
BEGIN:VEVENT
UID:90bbafd033c512f7590d844a0d65b449
SUMMARY:Run the London Marathon
DTSTAMP:20240421T080000Z
DTSTART:20240421T080000Z
DTEND:20240421T130000Z
DESCRIPTION:I'm running the London Marathon
LOCATION:London
END:VEVENT
END:VCALENDAR
it's not possible to create a QR Code using the Affinity apps because of the single-line format which results in a No Usable Data Found error message when scanning the generated QR Code using the iPhone camera's built-in QR Code Scanner...
Note: I've not tested this on Android but my assumption is that this will result in the same issue...

Technically no because with dashed lines you don't have access to the pressure map so all you see when making changes to a dashed using the line width tool is the entire dashed line becoming thicker or thinner however, if, after applying varying line widths on the dashed line you convert it back to a solid line the line width changes are honoured...
So even though you can't visually see the changes being made to a dashed line, the underlying changes are made but can only be seen visually once converted back to a solid line. It begs the question 'should it be possible to apply different line widths to dashed lines', i.e., should the pressure map also be available for dashed lines as well?

It's quite likely I added it thinking about it, more so as there isn't one in the Pixel Perona of Publisher. I think the keyboard shortcut in Photoshop is Cmd H so that may be more appropriate for those Photoshop users with muscle memory...

There appears to be no default shortcut on Windows.

Spread Properties is accessible by right-clicking a page which makes sense. It was just supposed to have been removed from the menu - I hadn't noticed it being in the other persona because I'm not a persona user.
I asked about it at the time the change was made because I thought there was still value in it being in the menu. You can delete a selected page from the menu so why can't you edit its properties from the menu? But I see the wisdom in the decision now - editing page and master spread properties is an edge case and doesn't need to be so visible and hiding the command guides users to editing the document properties which will avoid errors. Those who really need to edit spread properties but don't know about the contextual command can still do so through document setup.

Hi @Hangman,
Good spot, I've logged this with the developers for correction.
I think 'Spread Properties' is it's own separate dialog and should remain as such when accessed from the pages panel. It gives specific config settings for amending the properties of the spread, whereas Document setup contains tabs relevant to the entire document scope such as colour space, model etc. that are not necessarily relevant to the selected spread(s) I've chosen to amend.

Hi @Hangman, thanks for the welcome.
When I hit export & the area opens up I have it on pdf1-2003x , mark it for  bleed & mark it all pages. Where is the layers panel connected to exporting?
 
I'm new to a Mac now using v2( from v1 being on a deskstop). Could the migration to the new version of the file be causing confusion? 
 
Also has page setup been swallowed in version 2 by tabs on offer under document setup ? 
 
The large document has to be saved as single for printing.

Thank you 
 

Pretty fun and fast to work on clean line art with this tool I got to say!

URI schemes are not QR code specific. The QR code just makes them "readable". It's up to whatever app/tool reads the QR code to handle the URI.
The official registered ones are available here > https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml, but I'm sure there are many other unofficial ones. 

Try...
MECARD:N:Cook,Tim;ADR:One Apple Park Way, Cupertino, CA 95014, United States;TEL:+14089961010;TEL:+17702313820;EMAIL:tim.cook@apple.com;URL:https://apple.com;NOTE:”How much wood would a woodchuck chuck, if a woodchuck could chuck wood? He would chuck, he would, as much as he could, and chuck as much wood as a woodchuck would. If a woodchuck could chuck wood.”;; MECARD:
N:Cook,Tim;
ADR:One Apple Park Way, Cupertino, CA 95014, United States;
TEL:+14089961010;
TEL:+17702313820;
EMAIL:tim.cook@apple.com;
URL:https://apple.com;
NOTE:”How much wood would a woodchuck chuck, if a woodchuck could chuck wood? He would chuck, he would, as much as he could, and chuck as much wood as a woodchuck would. If a woodchuck could chuck wood.”;;

Is there a complete list of all the Payload structure options available for QR Codes, e.g., email, MMS, vCard etc., or is it restricted to URL, SMS, GEO Location and WIFI?

Is there a complete list of all the Payload structure options available for QR Codes, e.g., email, MMS, vCard etc., or is it restricted to URL, SMS, GEO Location and WIFI?