Jump to content

will w

  • Content Count

  • Joined

  • Last visited

  1. This issue still exists in 1.7.1. (though many far more important issues were fixed---palm rejection, issues with gestures and touch, etc.)
  2. I have a project that I previously saved to iCloud, then opened from iCloud so it would save to the correct location when I hit Save, or exit the project (in theory). A day or so after updating to 1.7.1, AD crashed for the first time ever (I think). The file was still open in the document browser, and had only reverted back by 10 mins or so of work. So I reopened, and re-did the work, then I hit Save just to be safe. Not long after it crashed again, back to same spot as before (so the Save did not work). I thought that since it was going back to the same spot each time it was saved at least to that spot. I closed the document, as I thought restarting might help with the crashing. As it turns out, the document had not REALLY been saved for the last 9 days. When I reopened from iCloud the version there was 9 days old. Why is AD not saving to iCloud? I originally opened the document from that location, which as I understood (and as I had checked before), was the correct way to get around the fact that the "default save location" setting does not actually work. Also, why does the "default save location" not work? If I create a new document, then I hit Save, shouldn't that save to the default save location? If not, then what is the point of such a setting? This setting was originally set to On iPad, and it seems this worked at one time, as I have an Affinity folder (with logo) in my local files, and in this folder is an old document that I don't think I saved myself. But at some point it stopped saving to that folder, and I guess (based on some things I've read), started saving things to the "sandbox," which is as good as throwing them away apparently. According to iPad settings there are 74mb of AD Documents and Data... where are these? Finally, one last desperate question: Is there any hope of recovering the work that was lost when I closed the document? Also, why would AD not tell me that I'm closing a document that has not been properly saved? Isn't this basic stuff? Thanks.
  3. Hi Sean, Update: If I select "Place Image", then place the image and double click on it to edit/add to assets, then click the <-- button to return to my document, the grid is gone. When I select "Grid" to turn it back on, the show grid button is already activated, and I have to click then unclick to reactivate the grid. I guess maybe as far as AD is concerned, moving to an embedded document and then returning to main document is the same as exiting the document then reopening, so might not be different than the issue already discussed. On a side note, when I return from editing the embedded document the main document is always highly pixelated until I pan the canvas. This happened in previous versions as well, though, so I assume devs are aware of this bug? Also, I have had a lot more trouble lately with failing palm rejection, gestures being interpreted as non-gestures, and even eratic behaviour when trying to pan/zoom (also panning and zooming is often not smooth or fails or ends up moving an object). I think at this point the most egregious issue is this, plus the fact that the "touch for gestures only" option doesn't really work at all. Thanks!
  4. Quick addition: I am finding that the grid also sometimes turns off while I'm working. When I go the the menu and select "grid", the show grid button is on (highlighted), and I have to turn off then on to get the grid back. I'm not sure what I'm doing when the grid goes off, as I have not noticed it when its happening---I just notice at some point that its gone.
  5. Sorry, by a toggle button I meant a button that stays on the screen (like the snapping toggle button lower left side), so the grid can be quickly toggle off and on. In general, it would be great to be able to customize what tools have dedicated on screen buttons.
  6. I was very happy to see arrowheads introduced in the 1.7 update, but somewhat disappointed with the execution, in one important respect. Namely, the corners of arrows should be (slightly) rounded, or have the option to be rounded. For example, here is an arrowhead created by Designer (left), and one I drew (right). arrows.pdf As proof that sharp arrows are a mistake, please look closely at the icon for the Selection and Node tools in Affinity Designer, both of which are rounded arrows. Ideally, the solution would be to make an arrowhead a separate object (but somehow attached to a stroke), with their own fill and stroke. Then a sharp arrow would be an arrow with no stroke, and the rounded-ness could be controlled by adjusting stroke (and the color of an arrow could be different than the curve it's attached to---another missing feature at this point). Also, it would be nice to be able to adjust the width of an arrowhead, and arrowheads should (optionally) bend to match the curvature of the stroke they are attached to. For now, I'll stick to making my own arrows, but I would love to see this fixed in a future release.
  7. With 1.7, when I exit out of a document then re-open, or when I open Designer and select a document I have previously worked on, the Grid is turned off. This did not happen in 1.6. Also, it would be nice to have a grid toggle button somewhere, though that's more of a feature request. I am running latest version of iOS, iPad Pro 11" with Pencil. Thanks!
  8. I strongly agree that "tough for gestures only" should mean what is says. I have a hard time imagining a reason that someone who has a pencil would want to use their finger to draw paths, edit nodes, or really anything at all besides gestures, and MAYBE moving objects (but only because it sometimes works better with finger than with pencil (i.e., doesn't resize when you want to move)).
  9. This is by far the most problematic bug in Designer. Note that if you watch any tutorial video made by Serif (where the pencil is used), you can see this problem happening. This is the most perplexing thing to me. The developers are clearly aware of the problem, and have been for a long time, and yet it persists. For a long time I just assumed that this was an unavoidable problem stemming from limitations of the iPad, but this is clearly not the case. Vectornator works virtually flawlessly in this respect (although I still use Designer, as it is superior in every other way, IMO). I have gotten used to just drawing paths to an approximate level of accuracy, then going in and adjusting every node. This is not necessary in Vectornator. Also, it seems that there is a very simple reason that Vectornator works and Designer doesn't: when a path is started in Designer, the node is not put down when the pencil touches, but rather when the pencil starts moving. In Vectornator, the node is established on contact, so it ends up in the right place. If you look closely, you can see that Vectornator also has a bit of delay, but it doesn't screw up node placement because the node is already placed when the pencil starts moving. This is really the most infuriating thing about this----that there is such an obvious solution (i.e., place node on contact, not movement). Also I will reiterate what many have observed above: that this has nothing to do with finger vs. pencil. You just can't see what is happening under your finger. Also, are people really using this app without a Pencil? It would be great to get some indication from Serif about WHY this bug exists, and what is being done, and what is the timeline of fixing it (or just acknowledging that it exists, for christ's sake). I have recommended this app to many colleagues, but I will probably stop recommending it until this problem is addressed.
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.