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

Search the Community

Showing results for tags '1.10.2.1187'.

  • 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 (Staff 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.5 Beta 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. I have described this above on the Designer forum as that was where pattern layer issues started the conversation and where I was pointed to the Publisher Beta, having posted response realised it might need a more Publisher related airing. Publisher Beta 1.10.21187 on Mac OS Catalina 10.15.7 27" late 2012 iMac As mentioned this behaviour is not in the current release version, just the beta.
  2. I first reported this back in October 2019 and that thread can be found back in the Pre-1.9 Bug Report section. Both the afpub and the text file in question were uploaded back then. (Hang_text1.afpib and Bible.txt) It's been 2 years since my last post on this subject, so I decided to give it another test with the latest beta (1.10.2.1187) Now it takes 55 minutes before I get control back, so there's been some improvement over the previous 1,5 hours. That said, having to wait almost a full hour to auto flow pure text is not satisfactory. Admittedly, it's 1800+ pages, but other users reported the process taking a handful of minutes, back in 2019. I assume this process is mostly CPU and memory intensive. I should be well covered there (6-core i7 and 64GB RAM), so I'm left wondering what's causing this. Any thoughts, devs? Edit: This should probably have been posted in the beta section. Feel free to move.
  3. This is something I haven't noticed in previous versions. In a 323 page 6"x9" document, the main window scrollbar only takes me as far down as (physical) pages 286/287. Never past that. If I use the left-hand Pages display to scroll to the bottom of the document, the main window scrolling behaves as expected from that point onward. And yes, I have waited a while to see if it clears up, i.e. the program is busy computing something. This happens on two computers. Windows 10 - 64-bit
×
×
  • 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.