Jump to content

andy-in-mke

Members
  • Content Count

    38
  • Joined

  • Last visited

About andy-in-mke

  • Rank
    Member
  • Birthday 02/04/1960

Profile Information

  • Gender
    Male
  • Location
    Milwaukee, Wisconsin, USA
  • Interests
    The Mac, cats, politics, writing, web design, science, history, philosophy, etc.

Recent Profile Visitors

558 profile views
  1. I did not save the file to the cloud until after the corruption problem arose. Prior to that it was in a folder on my desktop. Thank you for looking at it. Not sure what I’ll be doing at this point. I am actually seriously considering rebuilding it. I have pdf exports from it that I can use for that purpose. If I rebuild it, one thing I’ll do is rasterize any imported objects on which I used AP’s tools (which I love by the way, but many of them didn’t print out properly at the service bureau we use -- there are tons of them in the file, and I suspect they may also have been a factor in the file corruption).
  2. Hi Pauls, Hopefully you see the afpub file. I uploaded it by itself last night. Andy
  3. Pauls, I don’t know if the upload got interrupted. My wifi setup here is poor and a constant source of trouble and irritation. I’m not in charge and there’s not much I can do about it. And the file of course is very large. I uploaded it at night and went to sleep before it was finished. The next day it LOOKED like everything got finished. Also, I’ve never shared a folder with subfolders in it before. Do you have to separately share the subfolders? Andy
  4. Hi Pauls, I just sent you the folder with the AP file and supporting graphics. Thank you for looking at them. Some possibly relevant information: When I finished the project, and before I saw the error message for the first time, I moved the folder with the whole project from the desktop and renamed it. I did NOT rename the folder in which the supporting graphics are kept. Andy
  5. Carl, I renamed the folder where all the project graphics are stored and got the same error message, alas. Andy
  6. Yes, it DOES seem strange that the backups were also corrupt. I’ve been working on this file on and off for weeks with no problem. The images are linked. The total size of the project is a little over 3 GB.
  7. macOS Mojave Affinity Publisher 1.7.1 After weeks of working on a very large coffee table book file, my boss, who was struck by the small size of the exported pdf from the original AP file, sought reassurance from me that I was not using a low pdf export setting. I was going to open the file and show him the setting, when I got this very unwelcome error message from AP (see attachment). I was also quite literally singing Affinity Publisher’s praises at the time. As I write this I am unable to open the file. I recovered older versions of it with Time Machine and got the same message. Weeks of work are potentially gone. Because of the size of the file I'm uploading it to Dropbox and will send an invite to whoever I need to at Affinity Serif (Dropbox tells me the upload will finish in 8 hours). I’ve searched your forums and have come to understand that this is not the first time this particular bug has raised its ugly head. Would appreciate your help with this. Andy
  8. Hi Walt... First, yes, the little screen grab you made is indeed what I was talking about. Second, since I made this post I’ve been able to finish the work I was doing – a highly-formatted multi-page index – without having to type everything in from scratch. What I’ve learned is that if I work meticulously and carefully set up my text styles, I can get my work done in Affinity Publisher. What I’m still puzzled by is why AP acted the way it did when I first tried to change the number of columns in my text box. I converted my movie to an mp4 by the way, if you’re still curious about it. What it shows is the new text box with text already pasted into it from another program (Swift Publisher). You can see the I-bar cursor at the very end of the fifth line of text. First I move the mouse arrow in a circle around the I-bar, just to show you where the I-bar is. Then I move the mouse down and to the right, to change the number of columns, from “1” to “2”. What happens to the text next absolutely confounds me. What I expected would happen was that with each click in the number of columns the text would be evenly divided into an increasing number of columns. Instead it looks like in response to my click, AP automatically inserted a column break right below the top line of text. Why on earth would it do that? In any case, thanks for your interest/response. Andy Incomprehensible Text Box Column Behavior.mp4
  9. I’ve tried clicking on the video attachment and it doesn’t even show up, much less play. I have no idea why this is happening.
  10. I have a large volume of text I wish to format into 4 columns over a two-page spread. I copied the text out of Swift Publisher, and pasted it into a single column text box in Affinity Publisher, thinking this would be a routine operation. Instead it has turned into an ordeal. As you can see from the movie I’ve attached, when I select the text box and click on the little column adjustment tool, the text does not reflow in anything remotely resembling a logical way. I thought maybe the text block had picked up some weird invisible characters/artifacts in Swift Publisher, so I dropped it into a TextEdit document first and converted it to plain text, THEN copied it into AP. This had no effect whatsoever on the problem. I feel like I’m going to have to retype it from scratch to get what I want, and what I want does not strike me as anything fancy, or complicated, or unreasonable. This looks like a bug to me. Is there a fix? Thank you for your help. Incomprehensible_Text_Box_Column_Behavior.mov
  11. Hi Chris, I know you left your response to my question almost a year ago but I didn’t see it ’til now. Just wanted to let you know that unticking the embed metadata option did not solve the problem, alas. Thanks anyway, Andy
  12. I’m sorry, Polygonius, but I don’t understand what you’re trying to say in your post, and that’s why I didn’t respond. Keep working on your written English skills. Take care. :-)
  13. R C-R, Sorry I haven’t responded to your comments sooner... I apologize, and thank you for your feedback. As for which app I used for the screen shots, I used the standard OS X screen cap function. I do not know what resolution that is -- Does it depend on the native monitor resolution? The thing is I specified 144 dpi when I (a) created the original file in Affinity Designer and then exported it as a jpeg from AD and (b) opened it in Adobe Photoshop and exported it using Adobe's Save-for-Web function. The Adobe exported jpegs take up twice as much screen real estate as they do via AD. I prefer the larger Adobe jpegs. My workflow involves emailing these jpegs to my boss for his inspection, using the Apple Mail app. Your guess as to why this is happening (i.e. that Defining 100% scale in Preview’s preferences would solve the problem) turns out not to be true (see my new attachment). The bottom line is that however the jpegs display, whether in Apple’s Mail or Preview apps, they end up looking the same as Adobe-created jpegs in the end, when I post them in a web page. So you can say it doesn’t matter. It’s just that I don’t understand what’s going on. It’s annoying to me but not truly important, and I can live with it. Andy
  14. As you can see from the attachment, the same file displays at different pixel sizes depending on whether it was initially exported from Affinity Designer or Photoshop. My question is why. Why won’t the jpeg exported from Affinity Designer display at the larger Photoshop size? Does anyone have any idea? Is there any box I can check so that AD matches the Photoshop display size? Thanks.
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.