Jump to content
AdamW

Affinity Publisher Public Beta - 1.7.0.238

Recommended Posts

Please Click here to download the latest beta for macOS

Status: Public Beta
Purpose: Stability and General Testing
Requirements: Mac OS 10.9 or above

Hi,

We are pleased to announce that Affinity Publisher build 238 is now available as a manual download from the link above and on auto-update.

As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity where you may be adversely affected by the application failing, including the total loss of any documents. 

We hope you enjoy the product, and as always, if you've got any problems installing or running up, please don't hesitate to post in this thread.

Any problems actually using this version please make a new topic in this forum and we'll get back to you as soon as we can. Please feel free to leave general suggestions and comments in the Discussion Forum

Many thanks for your continued feedback.

---

Multi-language UI

We now have localised text for all of the languages we intend to support at release, and the Preferences UI to switch language has been enabled.

However, we are aware of quite a large number of issues currently with UI layout and missing translation text. If you wish to log an issue on the forum that you think is purely a translation issue (i.e. UI layout, text truncation, missing translation, incorrect translation) we would be grateful if you could make a post in this specific thread.

---

Hyperlinks

We have our first pass at support for Hyperlinks. You can place Hyperlinks on text or other items in your document and create anchors for them to target. You can also create hyperlinks to document pages or internet URLs etc. These hyperlinks will export to PDF, though be aware not all varieties of PDF support interactive features. This feature is mainly driven via the Menu, Text > Interactive and the Hyperlinks Panel, View > Studio > Hyperlinks.

Additionally if you create a TOC or Index and request hyperlinks on export the TOC or Index will be furnished with hyperlinks as appropriate.

---

General Fixes

Please note that documents saved in Build 238 will not open in Build 227 or earlier. We suggest you work on a copy if your document is valuable to you.

Main Window, Menus, Panels, Tools
Grouped and ordered blend modes in various places in the UI
(Win) Fixed issue with Noise slider in Layer Effects causing hang
Convert to Picture Frame/Text Frame missing for right-click on any selected shape.
Added button tooltips to Fields panel for clarity
Fix to snap Picture Frame content to frame
Fix for unwanted page change when placing a guide
(Mac) Fix for currently active page not being highlighted correctly in Light Mode
(Win) Fix for poor Glyph Browser selection highlight in Light Mode
(Win) Fix for spot colours losing spot attribute when edited
Grouped tool shortcuts now default to using the Shift key to cycle. Option in preferences to revert to old behaviour.
Fixed possible crash with HSL Adjustments
Fields Author field can now be overridden by supplying default with no documents open
(Win) Fix for TOC / Index separators not accepting preset entries
(Win) Fixed slow resizing of side panels

Pages and Master Pages
Fixed issues moving single pages with facing masters
Select All no longer selects master page content
Fixes for Find and Replace with master text frames
Fixes for TOC and Index issues with master pages
Fixed context menus for master page items on regular pages
Fix for Text Ruler not showing with detached master page text frames
Fix for Auto-flow with master frame content
Fix for Resource Manager not showing resources in detached picture frames
Fix for guides not being inherited when master applied to master

Text and Tables
Fix for Auto-Capitalise being too keen to help
Added a Text Tool context toolbar shortcut to access Text Frame panel
(Win) Fixed List Increase / Decrease Level shortcuts clash
Added 'No Style' to Find and Replace Paragraph Style popup
Fix for Text Styles options not updating based on selection
Fix to expand Text Field contents for copying to clipboard in non-native formats
Fixed Arial Black confusion
(Win) Text Styles - Added optical alignment settings to Text Style Editor
Fix for incorrect Text Wrap in scaled Text Frames
Fix for text selection across spreads with master text frames

Import, Export and Printing
Placing text via File > Place now honours resizing aspect preferences
PDF Export now has the option not to export layers
Fixed to warn when printing if crop marks are requested but don't fit to paper
Fixed source of crash when exporting specific documents to PSD
Updating a placed multi-page pdf now maintains chosen page number if possible
Fix for current page not being selected when using 'Current Page' print range
Fix for Bleeds failing to export to PDF when selecting specific Artboards
Fix for image resources not saving and loading their relative paths properly
Fix for Bleed not set when importing Designer document with Artboards

Setup
(Win) Fixed high DPI setup failure
---

Earlier Release Notes Beta 227

Share this post


Link to post
Share on other sites

ACE!


MacBook Pro (15-inch, 2.53GHz, Mid 2009)

8 GB 1067 MHz DDR3

Ugee 19" Graphics Tablet Monitor

Mac OS 10.11.6 El Capitan

Mainly use Affinity Designer & Photo 1.6 Publisher 1.7.0.145 Beta

 

www.bingercreative.co.uk

Share this post


Link to post
Share on other sites

Hello @AdamW 
Thank you so much for this and also for the server you uploaded the software to.
I'm sure it won't make me trouble downloading.

3 hours ago, AdamW said:

Please note that documents saved in Build 238 will not open in Build 227 or earlier. We suggest you work on a copy if your document is valuable to you.

Well Dear, we don't all upgrade even when we know we go through a Beta cycle, so i suggest you include into the Save As a possibility to save project as old supported file format similar to what Microsoft office does or you can add an additional tab into the export so we can export as ... old file format.

Just in case i may forget about it !
Please you should consider to make it possible (for those doing book edition) to organize pages according to its nature/importance but also it should be possible for us to add separators between different sections of the same document, here i mean APub should allow us to edit very large document and when a document (book, report etc.) get very large we should be able to organize into sections and even we should be able reorganize an entire section by selecting then drag and drop where we want it to be.

I mean this will make APub a real challenger to already established solutions but also will bring ease of use.
I will develop this (if i have time) into the suggestion topics for APub but for not i drop it here so that i don't forget about.

Blessings !


Never be the Same Again !
MacBook Pro (13-inch, Mid 2010) - 2.4 GHz Intel Core 2 Duo - 8 GB 1067 MHz DDR3 - VIDIA GeForce 320M 256 MB

MacOS High Sierra 10.13.6  - Affinity Designer + Affinity Photo + Affinity Publisher + Snagit 2019 + Camtasia 2018 + Movavi Video Editor Business 15

Share this post


Link to post
Share on other sites
4 minutes ago, Uncle Mez said:

Well Dear, we don't all upgrade even when we know we go through a Beta cycle

You use these betas  at your own risk. If you use it for production that is your choice.

No, developers should not have to do that (Save as...).

Share this post


Link to post
Share on other sites
21 minutes ago, Uncle Mez said:

Well Dear, we don't all upgrade even when we know we go through a Beta cycle, so i suggest you include into the Save As a possibility to save project as old supported file format similar to what Microsoft office does or you can add an additional tab into the export so we can export as ... old file format.

It was never guaranteed that files created in one version of the beta would even open in the next version.

The fact that .238 can open files from .227 is already more than we knew we could rely on.

I could see asking to save in a format compatible with 1.6 (if there *was* a 1.6 version of Publisher), but expecting backward compatibility with previous betas that are not considered production versions of the software is going a bit too far.

Share this post


Link to post
Share on other sites
6 hours ago, AdamW said:

 

We have our first pass at support for Hyperlinks. You can place Hyperlinks on text or other items in your document and create anchors for them to target. You can also create hyperlinks to document pages or internet URLs etc. These hyperlinks will export to PDF, though be aware not all varieties of PDF support interactive features. This feature is mainly driven via the Menu, Text > Interactive and the Hyperlinks Panel, View > Studio > Hyperlinks.

@AdamW, the hyperlinks feature is a great and welcome feature but as it stands, a text that has been made into a hyperlink appears the same as every other text.  There is no default styling of the archor text to differentiate it from other text on the spread.  It would be good to make the hyperlinks easily differentiable from the rest of the text

Share this post


Link to post
Share on other sites
3 hours ago, AdamW said:

Hi Uncle Mez,

We probably could have and should have avoided the 238 / 227 saving loading issue, but it was picked up late and since 227 will be as dead as disco in a couple of weeks anyhow, we decided to just roll with it. Sorry if it’s a pain.

Hi @AdamW please let's take it easy.
i'm not blaming you or the devs team or anyone in fact i'm raising something that seems logical if we consider the way of software usage.
That's why i quoted about the philosophy because it may be a deliberate choice and that also is good but just sometime there are leftovers in the kind of work you do which is massive and really respectable.

the case i raised is not like: You do it now ... or ... You do it !
but it is more like: Guys, it is normal that we have no Save As ???

@Seneca i appreciate your intervention and it is of good mean.
Please take it like i'm also sharing my experience, i don't know how to test a software beta or not without putting it in front line and pushing hard against the wall and see how deos it react. Maybe there is a different way of doing that but i don't know that other way.
I take everything beta (designer - Photo and Publisher) and i do my daily work with it and try to make my client happy, i'm not saying i don't find bugs or non satisfying stuffs but the fact of working with the tool everyday makes me sensitive of how the software have changed and also how it can be changed for good but also sometime the way i express it is not that accurate and i'm sorry for that.
Maybe i just made you or other people here in an uncomfortable position with my writings ... will try to make better content !

Blessings !


Never be the Same Again !
MacBook Pro (13-inch, Mid 2010) - 2.4 GHz Intel Core 2 Duo - 8 GB 1067 MHz DDR3 - VIDIA GeForce 320M 256 MB

MacOS High Sierra 10.13.6  - Affinity Designer + Affinity Photo + Affinity Publisher + Snagit 2019 + Camtasia 2018 + Movavi Video Editor Business 15

Share this post


Link to post
Share on other sites

I will be interested to know what efficiencies or functionalities that are baked into the new version 1.7 file format compared to the the eariler version 1.7 file format or even version 1.6 file format.  Perhaps, that would put a lot of these arguments to rest ;)

Share this post


Link to post
Share on other sites
9 hours ago, AdamW said:

Fields Author field can now be overridden by supplying default with no documents open

This was an important change.  Thank you!

 

9 hours ago, AdamW said:

Fix for Auto-Capitalise being too keen to help

:8_laughing:

Share this post


Link to post
Share on other sites
6 hours ago, Uncle Mez said:

Hi @AdamW please let's take it easy.
i'm not blaming you or the devs team or anyone in fact i'm raising something that seems logical if we consider the way of software usage.
That's why i quoted about the philosophy because it may be a deliberate choice and that also is good but just sometime there are leftovers in the kind of work you do which is massive and really respectable.

the case i raised is not like: You do it now ... or ... You do it !
but it is more like: Guys, it is normal that we have no Save As ???

@Seneca i appreciate your intervention and it is of good mean.
Please take it like i'm also sharing my experience, i don't know how to test a software beta or not without putting it in front line and pushing hard against the wall and see how deos it react. Maybe there is a different way of doing that but i don't know that other way.
I take everything beta (designer - Photo and Publisher) and i do my daily work with it and try to make my client happy, i'm not saying i don't find bugs or non satisfying stuffs but the fact of working with the tool everyday makes me sensitive of how the software have changed and also how it can be changed for good but also sometime the way i express it is not that accurate and i'm sorry for that.
Maybe i just made you or other people here in an uncomfortable position with my writings ... will try to make better content !

Blessings !

You can probably cooy and paste between betas as last resort if you need a document to continue working with the new beta. Not ideal but it usually works...


2017 15" MacBook Pro 14,3 w/ Intel 4 Core i7 @ 2.8 GHz, 16 GB RAM, AMD 455 @ 2 GB, 512 GB SSD, macOS High Sierra

Share this post


Link to post
Share on other sites
59 minutes ago, ronnyb said:

You can probably copy and paste between betas as last resort if you need a document to continue working with the new beta. Not ideal but it usually works...

It's only a problem if you wanted to revert to the previous beta for some reason, which of course we hope you don't (or in Uncle Mez's case, want to share a document with someone who hasn't yet updated). In general we don't guarantee loading in old versions anyway, it's just that with most of the recent incremental updates it has tended to be OK.

Taking a backup before working with a new beta update can never be bad advice. ;)

Share this post


Link to post
Share on other sites
14 hours ago, Uncle Mez said:

Maybe there is a different way of doing that but i don't know that other way.

@Uncle Mez, I didn't mean to be offensive in any way.

FWIW, I have also done a few projects with Publisher beta and that helped me to discover bugs, etc.

I completely agree that a concrete project is the best way to take Publisher through its paces.

What I don't think is right though is to compare Publisher to Word (a released product) which had a number of file format changes and needs to keep a lot of people happy especially those with legacy files.

Last thing we want is for the dev team to waste their time trying to keep previous formats in sync with the latest betas. The sand is still shifting under out feet and we beta testers have agreed to that. :)

 

Share this post


Link to post
Share on other sites
53 minutes ago, whitewolf7070 said:

Still hoping for the option to have paragraphs span across columns without having to create a separate text box, with all the text wrap settings and all. The ability to do this is about the only thing keeping me with InDesign. 

You can do that already, and have been able to since the first beta release, with a multi-column Text Frame.

When drawing the Text Frame, you can set the number of columns on the Context menubar. Or you can View > Studio > Text Frame where you can set the number of columns and the gutter values.


-- Walt

Windows 10 Home, version 1809, 16GB memory, Intel Core i7-6700K @ 4.00Gz
Affinity Photo 1.6.5.123 and 1.7.0.243 Beta
Affinity Designer 1.6..5.123 and 1.7.0.243 Beta
Affinity Publisher 1.7.0.238 Beta

Share this post


Link to post
Share on other sites
7 hours ago, walt.farrell said:

You can do that already, and have been able to since the first beta release, with a multi-column Text Frame.

When drawing the Text Frame, you can set the number of columns on the Context menubar. Or you can View > Studio > Text Frame where you can set the number of columns and the gutter values.

Walt, I think he meant having, for example, titles span across columns inside the multi-column text frame. I.e. having body text flowing in two columns but subheaders flow over the gap and the second column. This was included in Indesign some years back, and it's an ACE feature, especially when making books or ebooks, as then you can have your text flow automatically through the whole frickin' book and just have one master text frame on each page. The amount of the paragraph's column span (1, 2, 3, or all columns) is defined in the Paragraph style. This is a real power feature that I'm really looking forward to seeing in Publisher.

Thanks for the new version, looking forward to the one with Finnish hyphenation included ;) We can hacksaw it in, but native would be nice. The library is Public domain, after all.


iMac 27" Retina 2017, 3,4 GHz Intel Core i5, 8 GB 2400 MHz DDR4, OS X Mojave | Long-time Adobe veteran (I still remember Aldus Pagemaker, HA!), making the big move after going freelance. Running Publisher Beta along with Designer and Photo desktop versions. Loving what you guys are doing.

Share this post


Link to post
Share on other sites
9 hours ago, walt.farrell said:

You can do that already, and have been able to since the first beta release, with a multi-column Text Frame.

When drawing the Text Frame, you can set the number of columns on the Context menubar. Or you can View > Studio > Text Frame where you can set the number of columns and the gutter values.

Fairly confident he was referring to this:

 

Share this post


Link to post
Share on other sites
2 hours ago, Läppä said:

I think he meant having, for example, titles span across columns inside the multi-column text frame

Ah. Yes, that does seem likely. Sorry for my misinterpretation.


-- Walt

Windows 10 Home, version 1809, 16GB memory, Intel Core i7-6700K @ 4.00Gz
Affinity Photo 1.6.5.123 and 1.7.0.243 Beta
Affinity Designer 1.6..5.123 and 1.7.0.243 Beta
Affinity Publisher 1.7.0.238 Beta

Share this post


Link to post
Share on other sites

Found an oopsie.

Screenshot 2019-02-12 at 16.06.19.jpg


iMac 27" Retina 2017, 3,4 GHz Intel Core i5, 8 GB 2400 MHz DDR4, OS X Mojave | Long-time Adobe veteran (I still remember Aldus Pagemaker, HA!), making the big move after going freelance. Running Publisher Beta along with Designer and Photo desktop versions. Loving what you guys are doing.

Share this post


Link to post
Share on other sites
1 minute ago, Läppä said:

Found an oopsie.

These belong in separate bug report threads, and there is already one where this particular issue has been reported:

 

Share this post


Link to post
Share on other sites
24 minutes ago, fde101 said:

These belong in separate bug report threads, and there is already one where this particular issue has been reported:

 

Thanks. My bad.


iMac 27" Retina 2017, 3,4 GHz Intel Core i5, 8 GB 2400 MHz DDR4, OS X Mojave | Long-time Adobe veteran (I still remember Aldus Pagemaker, HA!), making the big move after going freelance. Running Publisher Beta along with Designer and Photo desktop versions. Loving what you guys are doing.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×