Jump to content

mad99

Members
  • Content count

    29
  • Joined

  • Last visited

About mad99

  • Rank
    Newbie

Recent Profile Visitors

102 profile views
  1. Hi Forum, In Affinity Designer 1.6.1 on mac os x, I designed a logo on transparent background. All is fine on mac os x apps. Preview, Photoshop CS, Affinity Photo, ... Only on windows Machine in Powerpoint and Paint, there is a white background displayed instead of a transparent background. In Windows Fotos-App the logo is shown without Background on black App-Background. Also fine. Maybe it is obvious, but I can't find any solution in App or here in Forum. - Why in Powerpoint and Paint is instead of «no-background» a white background? - Do you have some similar experiences or any work-around, so windows-user can use this Logo too in Powerpoint and Paint? - Do I have to set some special options while «export as» PNG? Thanks Martin
  2. Great it works (Posted in download-page) Nevertheless, a possibility to install the old version on few systems where current version (in future) does not work, would help very mutch in everyday life. Simply like this time, via a link in case of total failure of the beta. But instead of around 5 days to get an expiring time about 30 days would be great and help to continue and increase the enthusiasm about Publisher's Beta and to be part of Beta-Tester-Team. I am the last one who doesn't want to work with the latest version. But if it doesn't work anymore, a longer expiration time would be extremely helpful. For all involved: Imagine, several hundred beta users are without a functional application after a few days. How would that increase the pressure to get a hotfix out even faster. Work under time-pressure is not the best condition to do it error-free. But anyway, Publisher (Photo and Designer too) is a great product and I love to work with. I don't want to keep bouncing around this wish/suggestion, be silent and enjoy the work. Cheers Martin
  3. Hey Team, Thank you for fast hot-fix. On first glance: Saving issue in - 1.7.0.162 is fixed. Tried - to use *.afdesign File in Master and Pages. - to use *.afphoto File in Master and Pages. - to save the change. - to export to PDF. - to save as newname.afpub. All works fine. Great thank you Martin
  4. Hi MEB, I'm thilled about and really looking forward to it. Thank you for all the great work and tools
  5. A Zoom-Slider like that from «Navigator» would help. Would Enables quick changes according to current needs.
  6. 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.
  7. 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.
  8. 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
  9. 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
  10. 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
  11. @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
  12. 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
  13. @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
  14. Hey AdamW, Will write the answer in Topic Thanks
×