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

Search the Community

Showing results for tags 'afb-4000'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.4 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 3 results

  1. Hi, Not sure if this is a bug, or just a problematic implementation. The situation - I have a 230page+ document, every page is a separate placed pdf file. Those pdfs are produced in a different application. I want to make a univeral update, that requires replacing every pdf from the other application. So, in the other application, I run the script that saves out every page as separate files - it overwrites the old pages. Publisher seems to be over-enthusiastic as watching for changes for files, and comes up with a modal error for every file, as "unsupported file types", I suspect because it's attempting to read them before the other app has finished writing them. As well, it puts up a notification for every changed file: I ended up having to force-quit the application to get out of this. For a single page update, it will throw up this unsupported file type error approximately 3 times in succession once the new file is written out in the other application.
  2. I've run into this error many times. Finally caught a screenshot to show. Scenario. Photo book, photo source is Lightroom. Resource Collection folder. In Lightroom I edit the photo and export it to the Collection folder. AFPUB notifies the user that the file has been modified outside the application. The second notice is "Failed to Open File, File Type is not Supported." The photo is not updated in AFPUB document (not replaced with the edited version). However, all you have to do is to "Replace Image" with the very same image (.JPG) and all is fine. So the problem is that the file type is, indeed, supported when you replace the image. The earlier versions of AFPUB would automatically notice the change and apply the newly edited photo into the AFPUB document. No user intervention when the image is Linked, and the preferences are set to "Automatically update linked resources when modified externally" This is no longer working as expected. Something about the File Type.
  3. Hey Affinities, I have a feature request for Publisher: I'm working on a year book project with around 100 pages/each around 4 images. My workflow for the images takes them through Adobe Lightroom from which I export the images to the project's folder. I've set Publisher to "Auto refresh external ressources". So it often happens that I find an image needs an additional tweak when arranged with three other photos, so I make the change and overwrite the existing file (each image is around 10 MB). Here comes the catch/bug/feature request: Publisher correctly recognizes that the file has been changed, but doesn't give the system enough time to finish writing the file: an error pops up "file not readable"... So the FR would be: "Make the software try e.g. three times (with say three seconds inbetween) to auto refresh the file before throwing the error" or if the system can give the information: check if file is still being written, check for refresh afterwards... Cheers, Jan
×
×
  • 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.