Jump to content
You must now use your email address to sign in [click for more info] ×

Catshill

Members
  • Posts

    677
  • Joined

  • Last visited

Posts posted by Catshill

  1. On 9/5/2023 at 12:08 AM, Mulder said:

    Why do you need so many fonts, when you probably aren't using any more than twelve? You don't need that many. All they do is slow you down and slow down your computer when you need to pick a font. Having more fonts does not make you a better designer.

    Whilst it might take more time to have to look through a long list, having more fonts won’t actually slow down your computer.

    As a designer, I am often called upon to have a range of different fonts from different companies so again, I disagree with the above comment.

  2. 1 hour ago, Petrichor said:

    Hi all. A follow-up question: are text and image blacks handled differently? I set both my text and images to K100 black. This is confirmed by the Affinity Publisher color sampler. However, after exporting to PDF, the text is a very dark gray instead. The Mac Digital Color Meter identifies the image as 0,0,0 RGB (black), but the text is 26,25,25 RGB (dark gray). Any ideas?

    From the link posted above…

    “The blackest black you can get when printing in CMYK is C-75 M-68 Y-67 K-90. Yes, you can accomplish this by…”

    Highlighting the mono image and pressing the K button .

     

  3. @Dan C

    I've been investigating this issue and it is related to my NAS syncing.

    I run a sync job that duplicates my files to a NAS. Affinity (native and associated) files that have been copied to the NAS preview correctly but the original files do not. 

    If I pause syncing...

    Open the original file and save it with a different name it displays correctly.
    If I open the file, change it and save it with the original filename it does not display.

    I need to find out why the process of copying the files breaks the source (local) but not the destination (network) preview handling. From the perspective of this forum its not a Serif issue however so apologies for leading you down the garden path.

     

  4. The external link above refers to a hidden object not objects on a Master page. I would argue that behaviour similarities between hidden object and master pages is irrelevant here.

    Affinity Publisher allows you to apply double-page master pages to a single page and doing this should work as expected, not as above. We need clarification from a member of staff. 

  5. 19 hours ago, Dan C said:

    Thanks for verifying and I'm sorry to hear this -

    If you launch the Affinity app, does this change the behaviour?

    Out of interest, were these documents created in V1 of the Affinity apps, or V2?

    Does this work as expected if you create a new Affinity document in V2, save and close the file and then attempt to preview the document in Explorer?

    Do you still have the MSIX versions of the apps installed alongside the EXE versions, perhaps a beta version of the Affinity app?

    No

    Both. It makes no difference. 
     

    No

    No, I completely uninstalled them

  6. On 8/11/2023 at 1:29 PM, Dan C said:

    I'm certainly sorry to hear this as this isn't the behaviour we experience here - have you restarted your PC since uninstalling/reinstalling the Affinity apps?

    Please note you will need to ensure the document is not actively opened within the Affinity app, in order for the file to preview as expected.

    I've rebooted the PC and can confirm that without Affinity being run, the File Explorer preview window fails to display any Affinity native or associated files. PDFs preview fine.

    I've also tried...

    Options 1 to 5 from this site:  https://wethegeek.com/preview-pane-not-working-on-windows/

×
×
  • Create New...

Important Information

Terms of Use | 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.