Jump to content

basilic

Members
  • Content Count

    20
  • Joined

  • Last visited

About basilic

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Your document might contain possible errors that the Preflight Studio palette would mention. For convenience, a Preflight warnings popup will appear to let you review those issues/errors when you decide to export your file. However, clicking on the Open Preflight button is ineffective if the Studio Preflight palette has not been ticked beforehand (View/Studio/Preflight) to be visible as a panel on your interface. I suggest that clicking the Open Preflight button must open the Studio Preflight palette even if this palette is currently not ticked in View/Studio/Preflight.
  2. I fully agree with you as I used to do the way you described, having my own folders, and had no issue too. As a matter of interest, a PDF generated by the Pages app saved into the iCloud Drive Pages folder, opens with Preview. In my opinion, the issue is with the Affinity apps and their relevant default iCloud folders. As I said, a right-click on a PDF clearly shows it must open with Preview, but when you double-click on it, it launches the Affinity app that created the PDF. Might not be a Finder issue on its own as the Pages iCloud folder behaves OK.
  3. OK fair enough. As you tested it, it seems to me as a Finder bug. It clearly should not behave this way as the default app to open PDF is Preview as per the Finder "open with" settings. Whatever the folder it resides on, any PDF must open with the Preview app. Now if you drag your PDF file out of the iCloud Drive Affinity folder and put it in the root of iCloud Drive or in any other non-Affinity folder, it will then opens with Preview. The way Finder behaves with those iCloud Drive Affinity folders is odd: you will notice that you cannot save or put any txt file into them for instance. jpeg, pdf OK but txt no. So, any "compatible" files located in the iCloud Drive Affinity folder, will open with the relevant Affinity App. Clearly a bug to me. Don't you think?
  4. PDF exports saved into an iCloud Drive Affinity folder do not reopen with the Preview app, but the Affinity app that initially created the PDF. Assumptions: - I have an iCloud account set with iCloud Drive and Affinity Publisher, Photo and Designer applications have set their own folders in there. - PDF files genuinely open with the Preview app by default on my Mac. However: From any Affinity app, if you export any kind of PDF file into an iCloud Drive Affinity folder, when you double-click on it, it will not open with the Preview app, but with the Affinity app that initially created the export file. Strangely enough, in the Finder, if I right click on the PDF, the default app to open PDF is set to Preview. And it opens with Preview if I click again Preview from this contextual menu. But, if I straight double-click on the PDF, it will open the Affinity app that initially created it. If the PDF is then moved away from the iCloud Drive Affinity folder to anywhere else, it will then open properly with the Preview app if I double click on it. I managed to replicate this issue with all 3 Affinity apps running v1.8.1, on an iMac and a MBP both running Mojave. Grateful if someone can replicate this issue too.
  5. From the Text Frame Studio palette, in the General section, for the Fill and Stroke Colour selection, it'd be better if we could get a % value of the opacity when the slider is moved, as in the standard Colour Studio palette.
  6. Same here, actually on all the Serif 1.8.1 suite (Designer, Publisher and Photo) iMac 21.5 1920x1080, Intel Iris Pro 1536 However crystal clear on MBP with Retina display.
  7. As a matter of interest, it's actually even worse with QuarkXpress 2018 (see below). Some combinations of letters are not correctly handled by Quark even when using a single colour. I tried all calt variations, but no luck. Odd to see that there's no issue with non-professional-publishing application softwares like TextEdit or MSoffice Word. I would have thought the other way around...
  8. Appreciate your answers. I have tested other handwriting fonts like Cursive standard or SGCursive or ScolaCursive for instance and I don't face the issue I have reported. I could use one of those that are OK, but they unfortunately don't propose all the variants/glyphs as I'd like to. I then assume it's a bug in Publisher, as there's no issue in TextEdit or Word either. Hope this will be taken into consideration by Serif for a fix.
  9. Very difficult to reproduce but I have been faced to the same issue. For some odd reasons, it may happen that we lose the black line (columns heading) and column (lines heading) that handle the resizing of the columns/lines amongst other stuff (merge, insert, remove, ...). You can still update your table and write into cells but you cannot manage your table anymore. I had the issue many times (also with v1.7.1) and off the top of my head, when faced to it, even if I was creating a brand new table, I was still missing these top/left black line/column. I had this problem a couple of days ago when reviewing a table in a doc. I reopened it this morning and problem disappeared. Odd. macOS 10.13.6, Publisher 1.7.2
  10. I am using an OpenType font called Belle Allure available here : https://www.dafont.com/fr/belle-allure.font more specifically the Belle Allure CM In Publisher, the ligature and the other features of this font works fine as long as the word written is using a single colour. As a teacher, I mix 2 colours in words to emphasize sounds or syllables. When mixing colours, ie I write the complete word in black then I change the colour of one or two specific letters, then the ligatures are broken between letters of different colours. I tried all the variations in the Typography palette, but no change. See the third text block in the Publisher screenshot attached . In Word or in TextEdit, I don't have this issue. See attached. Any idea? macOS 10.13.6, Publisher 1.7.2, Word 2016 Edit: I tried copy/paste from Word or TextEdit to a new text block in Publisher, but no improvement.
  11. May I suggest you keep the same palette order in the Preferences pane of the Swatches (currently Application then Document then System), and in the palette dropbown choice in Swatches pane? This is not consistent between the two. I'd suggest this order in fact: document then application then system. Same improvement request for Designer. See attached. Publisher & Designer 1.7.2 / macOS 10.13.6
  12. Minor translation issue in the Export panel in the PDF tab when interface is setup in French. My setup: macOS 10.13.6, Designer 1.7.2. See screenshot.
×
×
  • 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.