neville

Members
  • Content count

    31
  • Joined

  • Last visited

  1. I see that someone has now completely removed the section titled 'The Future' from that page, without even acknowledging this forum post. Quite sheepish, really. No matter -- we can't all have courage.
  2. I wonder whether anyone at Serif has been assigned the job of keeping the Affinity website up-to-date. If so, it's curious that it says this under 'The Future': Following the huge demand for Affinity Designer for Windows, we’ll be bringing Affinity Photo to that platform too. https://affinity.serif.com/en-gb/about/
  3. I see that the flickering lines still happen when manipulating nodes in v1.5.3.69. Is the plan to fix this during the v1.6 development cycle?
  4. I see the same thing still happens with v1.5.3.69. Is it still on the list to be fixed?
  5. Thanks for the detailed explanation Patrick.
  6. Interesting to see that both Affinity Photo and Affinity Designer each initiate outbound network connections to the address crashes.seriflabs.com as soon as you launch them. That name was chosen to avoid suspicion about the reason for phoning home?
  7. Does either Affinity Designer or Afinity Photo have the ability to design and create icon files? I don't see an option to export to .ico format.
  8. Actually, that video was of v1.5.1 retail. Anyway, there is no change in v1.5.2.
  9. OK, let me rephrase then. It's obvious that the Affinity applications were developed as Mac apps, first and foremost, and then afterwards "ported" to Windows. That's why we see window control issues, rendering/re-draw issues, performance issues, etc. The code has started off being Mac-centric, i.e. Windows is not the primary platform that was targeted initially. I've noticed many of the same kinds of issues with other applications too (e.g. Scrivener), where the initial versions were developed on the Mac and the Windows versions came later. And as for my comment about lack of attention to detail: The developers fixed the bug in v1.5.1 where the window covered the taskbar when maximized. But when testing the fix, they didn't maximize the window and then look to see if the window looked right after maximizing it (i.e. they didn't look at the window controls). And then after that it went to your testing/QA team where nobody there maximized the window and checked to see if it and its controls looked right.
  10. Using v1.5.2 of AD: Open a file. Click on the Export Persona button. Close the file. Notice that you get a prompt saying the file was changed, do you want to save changes. It makes no sense.
  11. After maximizing the Help window for AD, the Maximize button doesn't change to a Restore button as it should. It remains a Maximize button. I think the devs (and testers) are not so familiar with Windows, and are more used to Mac. v1.5.1 covered the taskbar when maximized, and in v1.5.2 the window doesn't know that it's maximized. Basic stuff, sure, but lack of attention to detail.
  12. Out of interest, is the aim to have the version number for Publisher in sync with Designer and Photo (the way those 2 products already have version numbers in sync with each other)? If so, does that mean Photo and Designer will still be on version 1.x next year, or does it mean that Publisher will have its initial release as version 2.x ?
  13. What performance problems had you been seeing previously when dragging shapes?
  14. I've tried AD 1.5.1 on my other computer too, also running Windows 10. It has a completely different hardware configuration, with a discrete graphics card (NVIDIA GeForce GTX 660). Running the latest NVIDIA GPU drivers. And exactly the same thing happens there too when quickly dragging shapes. So it's safe to say that this issue affects not only integrated Intel HD Graphics, but also discrete NVIDIA GPUs. Which is hundreds of millions of PCs. I wonder how much the Windows version is tested internally, at Serif/Affinity.
  15. Thanks MEB, it sounds quite unlikely then, unfortunately. With this being quite a new application, and with the opportunity to start from scratch without any legacy cruft and legacy naming, it's disappointing that these kinds of things weren't carefully considered beforehand. Now, even at this early stage, you may be stuck with these inconsistencies forever.