Jump to content


  • Content Count

  • Joined

  • Last visited

  1. Thanks @vivera but it's just happened to me again. The file above was a Publisher file with some images. This one is a Designer file with no images at all. This never happened to me before the 1.9 update (related?) but now I've lost a total of 5.5 hours work. This truly sucks.
  2. Working on a 10MB file on an iCloud sync'd local folder. Same problem as listed here. Cannot now save the past three hours work. Really. What's the fix? This is seriously not a good look.
  3. Affinity Designer I find unlocking a layer challenging when I have hundreds of layers. For unlocked layers, Find in layers panel works a treat. But for locked layers this option is greyed out (I guess because the layer cannot be selected) and I have to scroll through all the layers looking for the one I want to unlock. What's the smarter way to do this? Thanks in advance.
  4. Looks like I'm having trouble with folders and files in general rather than Affinity applications specifically. So please consider this closed.
  5. Open Publisher. Click File. Mouseover Open Recent. And get the spinning beach ball. Just tested in Affinity Designer, and that does the same. Other applications on my machine do not. Mac OS 10.15.6 Latest versions of Affinity.
  6. Hi @MEB, fortunately, I haven't had to use Designer since my last comment here. Now I do. You noted back in January that "Something is wrong with object detection/selection." I agree! What is it? Some of my files work. Some don't, like the one I provided. Selecting the elements and pasting to a brand new doc doesn't fix it. So looking forward to learning what your dev team concluded. ?? Cheers.
  7. Hi @MEB, thanks for your questions, and apols for delay in responding ... I have been on hols. The file was created from scratch in Designer. Nothing imported except the odd jpeg (hidden).
  8. Thanks @MEB ... done. Not the most interesting / attractive file you'll have received :-)
  9. @gdenby, thanks for your question. When the line is selected (per the animated gif above), and I then select the node tool and Select All, the line that's selected simply has solid blue squares at each end, as expected. No orphan dots. Nothing else appears (or disappears). But now I can see how some of my lines got broken into two (per my 2nd comment in this thread). With the line selected, clicking anywhere on the canvas to the left or right of the line (and I mean far away) inserts a node on the line.
  10. Affinity Designer is currently a no-go for me until I can find a way to fix this. Such a simple thing wrecks my workflow. Just did a clean install to see if that would fix it. Unfortunately not. :-(
  11. Thanks @R C-R. I can confirm that when I have the move tool selected and click on a part of the canvas well away from anything, a vertical line gets selected that isn't part of a group. See the attached file.
  12. Now I find, when I can click on a line, that it's been severed into two lines at some entirely random point. This is most strange. Haven't seen anything like this in the couple of years I've been using Affinity.
  13. I'm running 1.6.1 on Mac and my select / move tool is acting a little crazy. Normally when I click on nothing, nothing is selected. Today when I do that, it appears to select a line seemingly at random. I have noticed that the line it selects is typically to the left or right of the 'nothing' I've clicked, but far enough away to know something is acting up here. Another symptom is that when that line is selected, clicking another object does not select it. No amount of clicking will work. I have to select with a drag instead. This is really annoying to the point of disabling. Has any
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.