mad99

A Zoom-Slider like that from «Navigator» would help. Would Enables quick changes according to current needs.

Thank you fde101 for your information. I grasped the last comment too, with the information «coming quite soon». Sure, maybe the versions aren't so strictly scheduled. Nevertheless, a longer runtime would probably mean very little extra effort for AP-devs or Release-manager but on the other hand mutch more flexibility and safety for everyone. The change in expiring-time would also reduce pressure to devs to publish fast version releases. Quite sure, it would help everyone.

Hi, maybe there is a way to change the thumb size more than the Pages>Options> «Small Icons» | «Medium Icons» | «Large Icons»? Usually in a document with lot of pages, some pages are quite similar. So the easiest way I found to add a new (quite simiar) page is to duplicate a existing one. Then move them to the right place maybe 9 Pages below. It is quite hard or near to impossible to recognize which page it really is where I have to «drag & drop the dublicated one». In Templates with page-numbers I can remember the targeted page/place and search them in the Pages-Icon/Thumbs subline-Info. But with the duplication the pages are move downwards and the page-number are changing. It is managable but not realy easy nor user friendly. Maybe I miss the setting to change the «zoom»-Setting of the 3 selectable settings (small | medium | large). If youm know a solution to up-size the thumbs - would great if you could share! If there is no setting for, would be great, if the size/zoom of thumbs in «Pages» could be changable more. So the Icon could be easy to recognize/match with the 1:1-Size Page. Would make daly work much more easy.

Hi again, Now, the end of the last working Beta is come. Because both 1.7.0.157 and 1.7.0.149 are expired. No operable or workable version for os x is left. I know the viewpoint from R C-R ( ). But I'm not sure if R C-R is an Affinity employee or the decision maker when it comes to making the software more user-friendly. Because the topic with included features request/suggestion has a wrong title, I create a new topc about this particular wish/suggestion/request. On macBook Pro with OSX the current Affinity Beta 1.7.162 is not a working solution, because the afpub files can no longer be saved or opened( ). Would be great if Affinity could discuss about a little longer expiring time from Beta-Apps. This could be easy with approach below or some similar solution: #################### PLEASE, do change expiring-date, so at least the previous version will survive 2 following versions! Proposal for calculation: exipreTime = releaseTime + 3x releaseIterations If your plan is publish all 4 Weeks a new beta-release. The second-last beta will expire 2 x 4 weeks after the release of latest version publishing-time. So when every four weeks: Affinity Publisher Beta_1.7.0.162 Release Date: 05.11.2018 Expire Date: 05.02.2019 Affinity Publisher Beta_1.7.0.157 (previous) Release Date: 05.10.2018 Expire Date: 05.01.2019 Affinity Publisher Beta_1.7.0.149 (second-last) Release Date: 05.09.2018 Expire Date: 05.12.2018 That would give the possiblity for your BETA-Tester to use at least 1 or 2 (if previous also has a fundamental bug) version back. AND for the business there is only 2-times of your release-time to make monetisation. Official BUY-Release: Affinity Publisher 1.8 (BUY-Release) Release Date: 05.12.2018 Last BETA will expire 05.02.2019 #################### Would be great to get a working Beta-App back or at least at next time to have not the same problem. Friendly regards Martin

Thanks R C-R OK, I see your point of view. But to be honest: I guess, I'm not the only one, who was waiting a very long time to the release of Publisher (or currently the BetaApp). And yes I use it for work with all the risk. I love the current state and have to deal with the risk and on the other hand I do beta-testing and reporting bugs. So, a little bit longer expiring-time would help to go step back if there is some bug, that makes the software totally unusable, or like this time does not allow to save the current work (What is almost the same in the first glance). With the older version it works still fine. And Publisher-Beta would be still usable. until the new bug-release will fix the problem. !!Be assured, I don't want to mess with an old version!! FOR SURE: I will update until the new release is out. This time manually, because there is no way-back in the App. Hope this will fix the save issue. Then If all is working, I will delete the Affinity Publisher Beta_1.7.0.149 and have fun. Pity with the short Expiring time -> But anyway - it was only a wish or feature request. Thanks anyway for all the work Cheers Martin

Additional Check: 7. Have «place» the same «designer-file» in 1.7.0.162 -> tried to save -> SAME SAVE-ERROR Obvious at least 1 BUG/PROBLEM with «USE embedded documents» Hope will help to catch the bug. Martin

@MEB: Maybe there is a way to adjust the release and expire practice of Beta-App a bit? This would greatly reduce the pressure and chances of total breakdown / interruption of work. Still don't touch Affinity's business model too much. I would be happy if something similar to the proposed formula could be planned or at least thought about. See here: Thank you for reading and the moment to think about it. Friendly regards Martin

So I have tested different approaches and questions: Here the answsers: 1. The file was written with 1.7.0.157 2. «Save with Document History» was turned off, when I had problems for the first time in 1.7.0.162. In the process of the Try & Errors, I enabled the function. 3. Today I desabled the «Save with Document History». Results: 1.7.0.162 Same Error -> enabled/disabled 1.7.0.157 No Error (with same test-file -> enabled/disabled) 1.7.0.149 No Error (with same test-file -> enabled/disabled) 4. Save network stuff: I work from Disk directly every 1 hours there are backup routines to save to Backup-Sticks (alternatively 2 different) (CCC) every 1 (30 min. shifted) there is a full-bootable-backup routine to save to external harddrive. (CCC) Time-Machine enabled to second harddrive. NO cloud or LAN files using. But all this copies/backups are only in the backgound. So I'm quite sure, this is no problem for Publisher. Also think so, because 1.7.0.157 and 1.7.0.149 works fine with absolut same approach. 5. «Also, if the original document is already on disk and you are trying to open it and save over it then posting the document could be very useful.» It is already on disk. Sorry I don't really understand the rest. Do you mean you would like to have the file in a private post - AdamW? 6. The Master-Page had included 2 «Embedded document» from Designer. Also in 1 Page from 30 there was a «Embedded Designer-Document» Have delete them all three in 1.7.0.162 -> SAME SAVE-ERROR Have delete them all three in 1.7.0.157 -> Reopen in n 1.7.0.162 -> NO SAVE-ERROR So I guess, it has something to do with the «Embedded Document» changing behaviour in 1.7.0.162. But maybe there are more than one «layer» that cause this error... Hope this helps to find the «real» bug (or all multiple layers). Cheers Martin

@R C-R: That sounds a lot like a problem to me TOOOOO! @AdamW: WHY the Hell? I understand: Affinity will expire the beta, to sell the Beta-phase the «non-Beta». BUT WHY THE HELL in such a short a time? #################### PLEASE, do change your practice, so at least the previous version will survive 2 following versions! Proposal for calculation: exipreTime = releaseTime + 3x releaseIterations If your plan is publish all 4 Weeks a new beta-release. The second-last beta will expire 2 x 4 weeks after the release of latest version publishing-time. So when every four weeks: Affinity Publisher Beta_1.7.0.162 Release Date: 05.11.2018 Expire Date: 05.02.2019 Affinity Publisher Beta_1.7.0.157 (previous) Release Date: 05.10.2018 Expire Date: 05.01.2019 Affinity Publisher Beta_1.7.0.149 (second-last) Release Date: 05.09.2018 Expire Date: 05.12.2018 That would give the possiblity for your BETA-Tester to use at least 1 or 2 (if previous also has a fundamental bug) version back. AND for the business there is only 2-times of your release-time to make monetisation. Official BUY-Release: Affinity Publisher 1.8 (BUY-Release) Release Date: 05.12.2018 Last BETA will expire 05.02.2019 #################### Im sure, your product will be (and is) such amazing, everty Beta-Tester will buy the price (if this is not extremely overpriced compared to «photo» and «designer»! All other, not willing buyer will have only 2 month (2 releaseCycle) left to have an amazing Beta-App. Cheers Martin

Hey AdamW, Will write the answer in Topic Thanks

Thank you MEB! Affinity Publisher Beta_1.7.0.157 WORKS fine!

Hey R C-R, thank you for the information. Will change all posts. Unfortunately I can't find a link to the previous version in your link. Maybe I'm blind. But the Links is relativ to the latest beta-version [https://affinity.store/update/macos/publisher-beta/1/] So in both links I will get the newest version 1.7.0.162. Maybe you could push me in the right direction, or direct my focus to the right place. Would be great! Thanks Martin

Hi, I have big problems with «save/save as» in current Publisher Version 1.7.0.162 (see: saving issue). At the end I had to reinstall an older version. Unfortunatelly this old version is 1.7.0.145. I don't know how old this is and if this eventually expire and stop working. So I'm looking for the last version 1.7.0.157. Do you have some working link to Affinity Publisher for OS X version 1.7.0.157. Would be great, you could share this. Thanks Martin

Hi, I like Affinity Publisher a lot. Unfortunatelly I stumbled into a problem with «save & save as». At the end, I had to reinstall an older version. In this process I glimpsed 2 points that could be improved: VERSION IN FINDER 1. In finder, the version is allways the same. Regardless of whether it is the beta publisher with version 1.7.0.145, 1.7.0.157 or 1.7.0.162! Please change the update/install process so the current version is also showing in the finder. OLD VERSION IN FORUM OR «ROLL-BACK TO PREVIOUS VERSION» IN BETA 2. In Forum, a Link to the previous version. So if the update has problems and the workflow is stopping, this would be an easy way to solve most of such problems with small effort. Obvious the red border is only to find it in this topic. Wouldn't make much sense in Forum. Maybe also at the end of the Topic/Post as small link like shown(without red border ). 2b. In Affinity Beta-Programm the "Emergency button": «BACK TO PREVIOUS VERSION». Same effect : Simply to be able to continue working. But mutch more dev-work. Please made possible an easy roll-back way. Thank you for all the great work on Publisher, Photo and Designer. I love them all three. Friendly regards Martin

Hi, I have big problems with «save/save as» in current Publisher Version 1.7.0.162 (see: saving issue). At the end I had to reinstall an older version. Unfortunatelly this old version is 1.7.0.145. I don't know how old this is and if this eventually expire and stop working. So I'm looking for the last version 1.7.0.157. Do you have some working link to Affinity Publisher for OS X version 1.7.0.157. Would be great, you could share this. Thanks Martin

Thanks fde101, Is not my intention to rstay on 1.7.0.145! Hope - next version will come out soon or - maybe someone will get a working link to last 1.7.0.157. Have tried with url-change from current link. But then the key-id is missing or no matching. So I can't figure out the right url. ...

Great! I have found a previous-previous version in forum «1.7.0.145» under https://s3.amazonaws.com/affinity-beta/download/affinity-publisher-public-beta-1.7.0.145.dmg. (If someone else is searching for.) AND -> it's unbelievable: This Version can open both of the files «written from 1.7.0.162 without problems. Also save-as is not problem. Have also duplictate the same page and the save and also the save-as is working like a charm!! - Maybe someone knows a link to a temporary hosted file of version 1.7.0.157? Then I could try out if this is working fine. Otherwise I have to wait until the next version. BUT I NEVER WILL USE THE UPDATE-BUTTON in tne APP! -> except if, ... 2 Small Feature-Request: 1. A Link in the next «current-version topic» to the «previous version». So if something went wrong, there is a simple way-back-routine. (Then I will use the Update-Button perhaps in future). Otherwise the manual download with parallel install will be my first choice ;o)) 2. In the Finder the version for 1.7.0.162 and 1.7.0.145 is shown as 1.7.0. Would be great if the shown version is same as the installated. So it would be mutch easier to see the different between 2 parallel installed or also to see what version is current installed, before any os x user update the app. Thank you for all the great work. Chears Martin

Hey Publisher is a great app, I love it. Unfortunatelly with the last Update I got a problem and can't find a work-arround. - Is there a way to go back to the previous installed version? - Did anybody know, where the updated version are to download? - Where I can see the history of installed/updated versions? ####################################### «Save» BUG: I have worked on an new Publisher File. Then the update-info poped-up. I saved the work. Then I updated the old version (unfortunatelly I can't remember wich one it was ;o(). With the Affinity Publisher Public Beta - 1.7.0.162 on MacBook Pro with OSX 10.11.6 I have always problems with save the file. After small changed the save-process works. But after a Page->Dublicate I cant save the current file anymore: Then I thought, I will do a new file with «SAVE AS». But this is also not possible: Stangly enough the file is written to the disk: First Time I guessed «YEAH, i have found a work-around!» But the joy lasted only briefly, next the save as file could not open with Publisher. The original FIle does not have any file-extionsions written like all the Files also in Designer and Photo. But the save-as-File has the extension «afpub». Seams to be OK, but at the end, there is some problem with: FIRST: the information about it should be already open fron an other application: So I shut down the Publisher, restart and reopen. BUT: The save-as File is not supported :o(( and the old original has not the current state inside. I treid also to shutdown the macbook pro. But after restart same behaviour. I tried also to delete the extesion But same «not supported» popup. Hope will help for debug. ####################################### BUT in the meantime: - Does anybody know a direct-link to old versions? - For safty futur: Is there a solution to install the next update in parallel to an old version? So it would be raly simple to go back to the last working version/only start the old one ;o)! Thank you for help and the great APP! Friendly regards Martin

+1 Many times or most of the time the order is twisted. Would be great to get some easy button or some command/script like in GIMP: https://docs.gimp.org/2.9/en/script-fu-reverse-layers.html. To do it manually is a pain and very error-prone with lots of layers.

Hey stokerg, thank you for help and link. The linked tut I looked 3 times before I post the topic. Also 4 other videos. But unfortunately it works fine with all the examples, but there is no hint or work-around- or do-it-the-right-way-example for use with symbols for menu-items with unSync + reSync the text-part, where only the text should change and the color, shadow, background, ... should stay synced for later layout-change. Maybe your attachment would help! But to be honest, I can't see any attachment in this topic. Do I have to look somewhere else or do something to activate the visibility of attached files? Would be great to have your very basic example to find the knot in my brain and got a way to untie it. Regards Martin

Hi, maybe I have overlooked the documentation or not found the particular video for this. I'am looking for the right way to work with AD Symbols for Navigation UX-Design. Does anybody know a tutorial, video or documentation-link so at the end I have the Symbol «menu-item-passiv». And this is one of 5-8 items in the Menu. Within every one I have to change the text, but still sync the color of the text, the width of the button, ... Only the text has to be different. I tried to use 1. the «create» button on symbol-panel to create a Symbol from the original text. 2. renabed the symbol to »menu_item-passiv». 3. Drag&drop the symbol to the canvas for second menu-item. 4. press «Sync» button in top-right corner of symbol-panel, it changed to grey. 5. Change Text to second Navi-Name. 6. Press «Sync» button again -> change to dark. But unfortunately, with this and a bit different approach, if I select the first «menu-item» and change the color, the second «menu-item» still has the original color. What I did or understood wrong? What would be the right way to use symbols for Menu-item in UX? Thank you for help Kind regards Martin

Hey, would be great, if Affinity Photo get's an easy to use possibilty like Photoshop with the Plugin «Image Processor Pro». So with one Click there could generate a couple of differenz image-sizes and image-types. There is 1 Original-Image «Test-Image» and at the end there would be 4 generated Images like: 1. 3200px (max width) with Name : Test-Image_xl.jpg 2. 1920px (max width) with Name : Test-Image_l.jpg 3. 1024px (max width) with Name : Test-Image_m.jpg 4. 640 (max width) with Name : Test-Image_s.jpg In «Image Processor Pro» it is easy to define with image-type, width, name-confention etc. See more details: https://forum.affinity.serif.com/index.php?/topic/36300-photo-export-persona-or-batch-prozess-for-different-image-sizes/ In batch-prozessing there is most of the necessary things; only the use of more files and the same kind of file-type is missing. Also with Macro it could work: If Macros could do also export/save stuff and presets could use individually.

Thank you for answer, Do I have to do a Feature Request or is this wish-fulfillment allready in the pipline? I think, it could be a nice feature, where Photoshop needs a Plugin and for AP it could be very handy work in current GUI/Solution. Only to define same file more then once Batch or use own presets for Export/Persona or expand the limits in macro recording to enclude export/save stuff. Would be great, not only for me I guess. Otherwise why should someone create a pluing «Image Prozessor Pro» ;)!

Hi, I'm looking for batch-processing in Affinity Photo like with Photoshop's Plugin «Image Processor Pro»: Tried to install «Image Processor Pro» Plugin without success, tried with Export Persona, but there are some restrictions to define own presets: https://forum.affinity.serif.com/index.php?/topic/11044-designer-export-at-different-sizes/ Also tried with Batch-Processing, but there is only one opportunity per image-type. In my workflow I would like to define 4 times a jpeg Like this: OriginalName.jpg 1. 3200px (max width) with Name : OriginalName_xl.jpg 2. 1920px (max width) with Name : OriginalName_l.jpg 3. 1024px (max width) with Name : OriginalName_m.jpg 4. 640 (max width) with Name : OriginalName_s.jpg Maybe I'm searching in wrong direction or some Export/Macro/Batch-Prozesses could combine together for a good workaround... Does anyone have a working solution for this task? Was looking videos, but no answer/solution found: Affinity Photo Exporting Affinity Photo Batch-Processing Affinity Photo Batch-Processing Affinity Photo Macros: