Patrick Connor

The earlier posts made in this thread before the feature was made available can now be found here

Hi @Affinityconfusesme, @Alfred, @Bobby Henderson, @Bryan Rieger, @kenmcd, @MikeTO, @ronnyb As you can see I have split these posts about the forthcoming Variable Fonts support made in this thread off into the Beta Members area. The original post by Ash will be repurposed to discuss the implementation of Variable Font support, and the talk here about other implementations (and OT discussion on Colour Fonts) would have got in the way of discussing the actual implementation and any bugs found. The new build 2.5.0.2415 including this feature will be made available soon, and can discussed here

I appreciate this is a grey/gray area but when a function has been refactored (like many existing publisher panels and this new panel) I think it's fair to assume that all old bugs might have been fixed as it's effectively new code. So if an existing bug does exist in an area where lots of changes have occurred and were specifically asking what you see, I'm ok with a bit of duplication. The reverse is true too. A long standing issue being tidied up in the refactoring may be worth mentioning too. The time not to mention existing bugs is when we haven't said there's been a refactoring or new functionality so nobody is surprised that nothing has changed

Here's a list of the bugs which have been fixed in the beta build 2.5.0 (2415) (fixes since the initial beta 2.5.0.2371) Please reply in this forum to comment on any fixes which are in this list (in particular to let us know if you notice that something we say is fixed isn't!) To report any new bugs please do that against the relevant new feature post, or if unrelated to new functionality in the Other bugs & issues forum. Changes/Bugs affecting all platforms "=" expression with Transform Objects Separately enabled is failing in Publisher [AF-2809] Bugs affecting Desktop (Windows and macOS) Clicking with the Line Width Tool inserts a 0% pressure point [AF-2769] Line Width Tool: using the Layer > Transform commands while the Line Width Tool is active leaves the pressure points misplaced (in their original position before transform) [AF-2768] Cannot use Line Width Tool in Designer Persona in Publisher when more than 1 page is present [AF-2766] Crash opening package and installing a variable font Hide / Show Others is not in Publisher's Layer Menu [AF-2083] Export persona > Document name and Document filename are empty for newly saved documents [AF-1496] Changing the Grid settings in the Develop Persona drastically reduces the image exposure [AF-1166] Bugs affecting Windows View transform is broken when one app hands off to the other Menu item Text>Show Typography Typography Panel should be listed under Windows > Typography Panel height cannot be adjusted Can't adjust the values in Transform panel using 'click + drag' gesture on the field label for 2 node straight open curves [AF-2213] Colour flyout slightly clipped on Windows Swatch names are not truncated 'Font Style' and 'Font Traits' language inconsistency between studio panels (mac fix to follow) AF-804 Bugs affecting macOS Incorrect lens being detected, Panasonic instead of Sony [AF-2822] Vertical Ruler is being rendered on top of the document tabs area when more than one document is open [AF-2796] Old Typography dialog (replaced by Panel) remains visible on upgrade from 2.4.2 to 2.5.0 Ruler Units are completely off/no longer start at 0 on macOS [AF-2760] Menu item Text>Show Typography Typography Panel should be listed under Windows > Text Text Style Editor: Unable to use 'Reset End characters' button when the field has focus on macOS Typography Panel: Hide irrelevant features checkbox is missing padding on the left hand margin [AF-2477] Bugs affecting iPad Thumbnail generation is delayed when using iPadOS 17, also affects menu for Live Doc [AF-466]

I think "(Best)" is being used here as the best balance between speed and quality (so "best performance"), although I can see that you might well assume (Best) meant "Best Quality"

That's great, can you please confirm that hardware acceleration is ON in the beta

We do not comment on whether ideas are accepted or rejected, otherwise everyone else posting in the suggestion forum would demand to know if their suggestions were accepted or rejected also. No you cannot demand copies of what you wrote. Keep your own copies if that's important to you

Please could you try the new 2.5.0 beta with Hardware Acceleration ON (join our beta program) and see if the problem has been addressed for you? Can you report your findings in this linked beta thread below made to share the results.

Please could you try the new 2.5.0 beta with Hardware Acceleration ON (join our beta program) and see if the problem has been addressed for you? Can you report your findings in this linked beta thread below made to share the results.

Please could you try the new 2.5.0 beta with Hardware Acceleration ON (join our beta program) and see if the problem has been addressed for you? Can you report your findings in this linked beta thread below made to share the results.

Please could you try the new 2.5.0 beta with Hardware Acceleration ON (join our beta program) and see if the problem has been addressed for you? Can you report your findings in this linked beta thread below made to share the results.

Please could you try the new 2.5.0 beta with Hardware Acceleration ON (join our beta program) and see if the problem has been addressed for you? Can you report your findings in this linked beta thread below made to share the results.

Please could you try the new 2.5.0 beta with Hardware Acceleration ON (join our beta program) and see if the problem has been addressed for you? Can you report your findings in this linked beta thread below made to share the results.

Please could you try the new 2.5.0 beta with Hardware Acceleration ON (join our beta program) and see if the problem has been addressed for you? Can you report your findings in this linked beta thread below made to share the results.

Please could you try the new 2.5.0 beta with Hardware Acceleration ON (join our beta program) and see if the problem has been addressed for you? Can you report your findings in this linked beta thread below made to share the results.

Please could you try the new 2.5.0 beta with Hardware Acceleration ON (join our beta program) and see if the problem has been addressed for you? Can you report your findings in this linked beta thread below made to share the results

In another attempt to fix the artefacts that can appear on Windows when developing RAW files in 2.4.x (with hardware enabled), we have changed the RAW processing pipeline. Please can you report in this thread any problems you continue to see with RAW processing when using the 2.5.0 beta builds. I will be asking users from some of these threads to come here and test the beta builds and post here (rather than their original 2.4.x thread)

When the font contains no alternatives/stylistic sets, I think it would be good to put that information in (grey) text rather than be blank and therefore confusing

That change just missed this build, thanks

note, 26 April 2022

Data Merge is not part of this feature, but we understand that it's likely to be a priority for implementing a way to achieve it

This thread is not for feature requests and barcodes are unrelated to QR code as far as implementing them, so this doesn't help advance Barcodes, sorry.

A number of Publisher panels have been completely refactored and so they may well have some unusual behaviour. Text Style Panel/Editor Paragraph Panel Character Panel Section Manager (macOS only) Please report what you find in regard to these 4 panels in this forum, thanks.

On Windows you will likely need to reset your toolbars (part of CTRL+Run-up) to get the new Line Width tool

The file format is not designed to be small it is designed with fast drawing in mind and image previews of all files are saved. "Linked" in an affinity file mostly means "watch out for possible changes" so the internally saved previews (at a number of sizes/zoom levels) are still there in the saved file, just not the original source file. Without those previews it couldn't draw quickly as you change zoom level. Perhaps we could offer a slower loading smaller sized "save minimal" that always regenerates the previews of a linked file on each load but that's not what we have currently, sorry.