Hangman

That is what is being asked for earlier in the thread, basically, the tool would greatly benefit from having a mini UI built around it so people could just enter the pertinent details, e.g., First Name, Last Name, Address, Phone Number etc., for a Contact QR Code or  Email Address, CC, BCC, Subject, Message for an email or a plain URL for a web link and so on...
This is still in Beta so hopefully, we'll see some improvements to the tool in a future release...

I'm unsure whether this is related to the scaling bug originally logged under AF-1288 and AF-1342 or a completely different bug altogether...
Both original bugs are listed as 'fixed by the developers in internal build "2.5.0.2317" by the Affinity Info Bot and appear in the 2.5 Beta Bug Fix List. While it does appear that the text scaling element of the bug has indeed been fixed there are still other issues present though these may be totally unrelated...
Changing the document dpi in v2.5.0 causes positioning and scaling issues with the inline image and table elements of the file which are not present in 2.4.2.

Scaling Bug.mp4   After changing the document dpi simply unpinning an element causes formatting issues not seen with the document's native dpi...

Unpin.mp4   Sample File
Scaling Bug.zip

Hi @Andy7771 and another warm welcome to the forums,
See how you get on with the attached files...
You will likely need to adjust them to suit the requirements of Autodesk Fusion but hopefully, they provide you with a good starting point...
Starfish.afdesign
Starfish.svg
 

Hi @Sean P,
Sorry, I meant to include the New Document window in the post... I realised I'd posted in the wrong thread since it's not specific to:
Text Style Panel/Editor Paragraph Panel Character Panel Section Manager (macOS only) so it looks like someone correctly split it out into its own thread...

You can see the effect error correction has when including a logo of differing sizes which highlights the benefit of being able to set the Error Correction level manually when creating QR codes, something which is supported in the QR Code generator library...
As has been suggested above, adding UI for all the different QR Options would make the creation of QR codes much more user-friendly...
You'll need to test by clicking on each image to view it full screen. Note: I've only tested these using the iPhone camera's built-in QR scanner.
Error Correction Medium | Quartile | High
All three QR Codes scan without issue...

 
Error Correction Medium | Quartile | High
The QR Code to the left set with Error Correction set to Medium fails to scan but with Error Correction set to both Quartile and High, the QR Codes scan...

 
Error Correction Medium | Quartile | High
The QR Codes to the left and centre set with Error Correction set to Medium and Quartile fail to scan but with Error Correction set to both High, the QR Code scans...

You can see the effect error correction has when including a logo of differing sizes which highlights the benefit of being able to set the Error Correction level manually when creating QR codes, something which is supported in the QR Code generator library...
As has been suggested above, adding UI for all the different QR Options would make the creation of QR codes much more user-friendly...
You'll need to test by clicking on each image to view it full screen. Note: I've only tested these using the iPhone camera's built-in QR scanner.
Error Correction Medium | Quartile | High
All three QR Codes scan without issue...

 
Error Correction Medium | Quartile | High
The QR Code to the left set with Error Correction set to Medium fails to scan but with Error Correction set to both Quartile and High, the QR Codes scan...

 
Error Correction Medium | Quartile | High
The QR Codes to the left and centre set with Error Correction set to Medium and Quartile fail to scan but with Error Correction set to both High, the QR Code scans...

Hi @anto,
Apologies, I edited my first reply because I realised the issue seems to be the 'Hidden Overflow' checkbox in the Text Frame panel... You can click the 'hide overflow special character' blue eye symbol to the right of the text frame which will uncheck the 'Hidden Overflow' checkbox in the Text Frame panel.
Why it's preventing all the text from being highlighted I'm not sure at the moment but assume this is a bug...

That does feel like a bit of an oversight as you have to do everything via the 'Manage Preset' panel...
Though they no longer perform as QR Codes of course... which tool/s did you use to manipulate the QR Codes out of interest?

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.

Just to add to my post before last...
When first launching Publisher, as mentioned above, it is not possible to select any of the text entry fields by clicking on their icon/label... this is also the case in v2.4.2, however, if I click in the Character panel 'Kerning' or 'Leading Override' text entry fields and hit the tab key, instead of tabbing between fields it adjusts both the Left and First Line indent values in the Paragraph panel instead...

Kerning.mp4

Great thread. Very useful to know.
Thanks!

I think what is being suggested is that the popup box where the URI is entered have a few tabs to build some of the common schemes for the user so that the user doesn't need to work out the encoding for all of them.
For example, iQR (on the App Store for the Mac), in addition to the URL option (which they label "WWW"), has tabs for Phone (enter a phone number), SMS (phone number and message), eMail (to address, subject and body), Map (enter an address and it looks it up using Google Maps or some other map service), Contact (first/last name, phone number(s), email address, web page, street address), Calendar (event name, when, where, etc.), PayPal/Bitcoin/SEPA payments (account, description, price, etc.), WiFi (network name/SSID, password, encryption type, hidden?), and Text.
 

 
It also provides an interesting range of formatting options to spice up the appearance of the generated codes:

 
Granted that this range of formatting options is probably a bit out of scope for a program that is not specialized in producing QR codes, but still thought I would point it out.  The more important thing to consider is to throw in the forms for a few of the common URI schemes.

It looks like the problem was with the "Scale with Object" setting.
I checked, it doesn't depend on the DPI of the document.
If "Scale with Object" is not selected, then everything is inserted fine, even if the resolution of the documents is different.
Thank you.

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?

I've not seen any glitches with Monterey either...

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... 

 

Hi Hangman,
I have logged for this to be fixed in a future update.
Thanks
C

Hi @Hangman,
I've now logged these discrepancies with the developers. 👍

I'm unsure if this is a 'by design' change but the Document Setup dialogue window no longer includes the DPI slider in the v2.5 Beta across all three apps...

It looks like the behaviour in Publisher is broken - I was doing the testing in Designer on WIndows. We'll poke this further.

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.

Fill colours and stroke weights are no longer updated in real-time in the Text Style Editor in the v2.5 Beta.
This affects:
All the Colour & Decorations options, Text Fill, Highlight Fill, Underline, Strikethrough and Outline The Decorations Stroke Colour, Line Weight, Fill Colour and Transparency

I'm assuming @danberlyoung's post on the first page of this thread...
I think it is intentionally blank since there are no QR Code Presets, you'd have to create your own for them to have any validity...

Thanks for the hint @Hageman, now I understand how it is meant to work