Jump to content

dkenner

Members
  • Content Count

    24
  • Joined

  • Last visited

About dkenner

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. > I consider myself a beginner in DTP. In order to improve my skills I'm doing a number of trainings on LinkedIn Learning. The person inspiring me the most is somebody called John McWade. You are about two weeks ahead of me, I just found this thread before asking the exact same question, from exactly the same LiL course, but with the letter L. McWade is excellent. Going through all of his courses. One piece of feedback that I have sent is to include AP in with the inDesign references if at all possible going forward. Now to figure this thread out... Ahhh -
  2. Patching for security reasons implies that it is no longer well protected. While not the forum to be discussing security best practices, if you have the ability to discern critical security patches from important, then waiting a day or two is possible, though my personal opinion that kind of delay primarily concerns iOS updates. OS/X, Microsoft, those should be on automatic update. The link is from one of the Five Eyes, and is a best practice. If a patch causes issues with AP, then Affinity has to address the issue, not the other way around. Consider it a variant of Maslow's Hierarchy of Needs...
  3. Just a quick note... https://cyber.gc.ca/en/top-10-it-security-actions No. 2. Always keep operating systems and applications up to date with patching... There is no benefit in keeping a system vulnerable.
  4. For what its worth, beyond the issue above, it has not repeated itself, and the application has been behaving rather will. Per Regina's comments, a "Cal-tech" sized computer won't make any difference if it is a memory issue or a programming bug in certain unique circumstances. That this thread is not overfilled with similar experiences suggests that what ever I did, was unique. Depending on platforms, it could be OS issues. I know my Windows platforms have experienced a lot of updates lately (though for ma AP is on OS/X).
  5. Correct, Publisher, on an iMac. But, while [ctrl-A] selects all of the text, if does not pick up the frame. I've tried. You can't just select the frame and copy that. Selecting and trying to copy the frame in the layers panel doesn't get you anything unless the text is selected, and even then, the result lands in the centre of the spread. Just curious really over the behaviour. While I would prefer the text frame to act like the image when copying and pasting, I am used to it. PS. Apologies for using [ctrl] rather than command. Starting on a teletype machine a very long time ago, the term "control" is deeply ingrained.
  6. Mostly a question of curiosity. When I cut and past an image from one document to another (a monthly newsletter for the local Land-Rover club), the image lands right where it was on the page of the originating document. If the image is in the upper right hand corner, it goes there, and not in the lower left, if that is where I put my mouse cursor and hit [ctrl-v]. OK, I am fine with this. I have moved the header image for whatever (upcoming events in this case). Next, I go and select the text frame under said header, as that will be copied and slightly edited. I cut and paste, and rather than going where it was on the originating document, it appears in the centre of the spread as a wide rectangle, rather than in the tall narrow column that it was. Now, one way or the other, which it is doesn't matter. it could be either, though I would really prefer that it landed where my cursor was, or at least the upper right hand corner landed there, or it was centred on my cursor. Doesn't matter. But why isn't it consistent between the two? I've noticed this with 1.8 & 1.7 too. (BTW, love the products, even if I am a neophyte at using them) Thank you, Dixon PS, I note the overload of pending support questions causing (presumably happy) delays on the part of Serif. Why are the questions forums for Photo, Publisher, et al all together in one huge forum. Is the behaviour that similar between the applications that this was deemed more efficient? PSS - Affinity Publisher 1.91, 2019 iMac, v11.2.2
  7. Happened twice with v1.9, once with v1.91 (last night). With v1.9, there was a crash report sent to Apple. No crash report with v1.91. Relaunched AP, and the same file re-exported without a problem. I must note that v1.91, and other two instances, AP crashed when the actual export was attempted. After the file name was entered and export pressed. The dialogue boxes up to that point worked fine.
  8. FWIW, Same as Ulysses here. Downloaded the file, opened, exported without any problem with APv1.9 with the latest OS (11.2) on a 2019 iMac
  9. A quick note. This has to be one of the most useful features I have seen added to a product in a long time. Having been doing club newsletters for the past year, in an organized, disorganized fashion, the packages feature allowed me to put the resources associated with the various newsletters together in one spot. I'd add that the process of finding all of the associated fonts and images, as over the months, despite best attentions, things migrate, only emphasized how useful this feature will be over time just for archiving and reusing resources. I agree with Emily in the 1.9 introduction video how useful this is. Thank you for putting it in. Dixon
  10. Let me solve my own observation after exploring some thing some more (new iMac (OS/X 11.2) to me, so not been through all of the preferences). iMac -> System Preferences -> General. Bottom grouping of options. There is a "Close windows when quitting an app" option. If this option is checked, The Affinity Publisher -> Preferences -> General -> "Reopen Document(s) on startup" will not work. Uncheck the iMac systems preferences box noted above and then AP's "Reopen Document... " option will work. Hope this helps others besides m....
  11. I note with APublisher v1.9 on iMac (latest OS) does not reopen documents that were open when it was shut down the last time.
  12. Good morning, A question. Previous to the last update of AP, when I copied text from documents or websites, and pasted into Publisher, it was pasted in the default text for AP, which at the time was Arial 12p. I was quite happy with this. After the update (and probably because I changed some default or something without realizing it) if pastes in using the font and size of the original. This is annoying, as I then have to change it to the new document font (Calibri 12p), general by highlighting the text, going to [Edit-Defaults-Factory Reset] and then changing the selection to calibri. 1. Where is the preference found to say the document is a particular base font, so I do not have to keep changing it? 2. Is there a way, setting, that would allow me to default pasting text into a document in the defined base font and not what some web page or other document was using? Thank you, Dixon
  13. Ahh, excellent. I had the same issue, but in Publisher on the iMac. Edit -> Defaults -> Factory reset solved it. Numberous videos did not, though I learned other things. Thank you,
  14. Publisher workbook arrived in Canada. It is excellent, and am slowly working my way through it. Quite pleased with the workbook. It is very well done and worth every penny.
  15. Very true, but you are limited to the number of lines per page for that XLSX file. When you are brining in an index for the previous year's articles (for a monthly newsletter), this xlsx file will exceed the 55 or so lines on a page. An ability to span multiple pages would be very helpful.
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.