![]() ![]() In the use case I mentioned, there are several bugs ( usability, performance, and plain bug old bugs □ SO YES HAVING TO WAIT 30+ SECONDS EVERY TIME YOUR APP CRASHES HAS AN IMPACT. Ruining the performance of expensive machines with poor software development decisions. Minimizing the problem (because you apparently are unaware that some customers don’t produce only basic documents) Saying that there is no solution (because the problem was created by Serif itself), Connor, stop insulting your customers by: Connor? In this case, the total number of Publisher reboots and manual interventions is 214!!! How ridiculous does it sound to you? That's almost 1.5 hours of waiting time, not including the manual interventions. In your opinion, how many unchargeable hours are wasted because of this, M. These reports are produced in 6 languages. Of course, this has to be repeated every time the customer asks for a modification. And as Publisher has no scripting capabilities, it must be done by taking the time of a real human that has to click everywhere for hours because of your bugs. So, I have to manually do it myself instead of taking one step (that would already last almost 2 hours just to generate the merge). ![]() As Publisher always crashes after 15 records (apparently the number of open files exceeds a limit somewhere), I have to manually create batches of 15 records, manually export the PDF, then close Publisher, open it again, then set the new batch for the next records, on so on. Each record has circa 250 linked fields pointing to SVG icons and plots. The reports are produced using a 10 pages layout for 200+ entities. I produce periodical complex reports with Publisher involving data merge. I use all Affinity products mainly for corporate publication. You might think that the problem is just happening when people open your applications, say once a day, which is acceptable. So, there is a solution, but Serif doesn’t want to acknowledge it. ![]() This problem was introduced by Serif when Serif decided that it was a good idea the change the welcome screen. You can’t just tell people that « there is no need to bump this thread » and call it a day. If we ever find a solution I am sure we will let you know.īy spending 4000+ USD on an 8-core 5 Ghz machine, I expect a substantial speed-up of my workflow. We know and there is no need to bump this thread. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |