Jump to content


  • Posts

  • Joined

  • Last visited

  1. While I found a few threads mentioning how constraints themselves seem to be somewhat broken, especially in combination with groups I couldn't find anything on Compound Constraints... which are highly messed up! They only work in individual cases, meaning as soon as you copy them or try to convert them into a symbol or anything they explode all over your document. And it's very easy to reproduce actually: Create an AFDesigner file Create to shapes Make a compound shape out of the two shapes (Alt + click on any of the Geometry options in the toolbar) Give one of the compound-sub-objects any constraints which turns the "Compound" object into a "Compound Constraints" one Copy the Compound Constraints object or turn it into a symbol and place an instance of that anywhere to have the sub-objects seemingly disappear (in fact they move to random locations) (Otherwise you can also try to copy or make a symbol of the Compound Constraints object in the appended file.) Since from what I could find out this bug or its relatives seem to be known for 2 to 3 years by now... is there any fix in sight? Or will it just stay broken for the foreseeable future? Constraints Compound Bug.afdesign
  2. Oh nice, that works like a charm 🤩 Thank you very much for that workaround! Since I created some Colour Palletes via Posterize and Gradient Map the first option wouldn't have worked for me, but the second is perfect!
  3. Is it possible to truly disable dithering for gradients? I only found the option in the performance settings, which is however limited to the preview rather than the final result. Meaning as soon as the gradient/s in question are rasterised the dithering is back on, which leads to undesirable results. (Preview) (Rasterized/Exported)
  4. I was painting in an AF Photo file (since it offers a few more possibilities than Designer does, even in its pixel persona; one example that comes to mind is the aforementioned flood select tool) and at one point decided that it would be nice to have different artboards for different designs rather than one giant canvas (and yes I know it's primarily the depiction, not the tech behind it). I hope that suffices as an explanation? Be that as it may -> He is wrong though: I just tried creating an AF Designer document, created (and moved) the artboards and layers and then switched to Photo, which results in the exact same problems. And before you ask: the same problems also come up in Designer's pixel persona (at least the Ctrl+A selection (with one of the pixel selection tools active) since the flood select tool does not exist in Designer). By the way, this took less than a minute to test; but I guess it's good that you ask, so not everyone has to try it on their own (If there's a way to edit my previous post with the step by step description I can add that there as well.) This should also have answered the rest of your questions and suggestions, right? Which brings me back to my previous question: how long might it take to fix that bug?
  5. Happy to hear that you could replicate it. Is there a way to avoid it (besides not using Artboards)? And can you estimate how long it might take to fix it?
  6. Start AF Photo Create a document (1920x1080px) Optionally Save the File File -> Edit in Designer Create 3 Artboards with the Artboard Tool (either by pressing the Insert Arboard Button (in the context toolbar) or by click-dragging in the main window) If you created the Artboards via Insert Arboard Button move number 2 and 3 away from their original positions File -> Edit in Photo Create pixel layers on each artboard, maybe paint a bit on each Press Ctrl+A with one of the pixel layers active As you can see, instead of the pixel layer inside the confines of the artboard, the original position and size of the artboard are now selected Ctrl+D to deselect With the Flood Select Tool click the empty area of the active pixel layer of the respective artboard As you can see, way more than the pixel layer in the confines of the artboard is selected; I hope this helps you with replicating the problem
  7. Oh, I created the artboards in AF Designer (sorry that I forgot to mention that) and then switched back to AF Photo.
  8. I can see the technical reasoning behind it and I think this wouldn't be as big a problem either if not for the second point I described, namely selection via Ctrl+A or Wand tool. However, I do not think this is ideal, since it's different from how the canvas works without artboards: Because without artboards it's impossible to paint outside the canvas borders, but possible to move layers (and the pixels on them) outside the boundaries with the move tool or by scaling them. I attached a file in which I created three artboards; in this case I used the Insert Artboard button in the context toolbar with the Artboard tool active and then moved the second and third artboard afterwards, however the problem also comes up when creating artboards via clicking and dragging with the Artboard tool somewhere in the document. To replicate the problem choose one of the artboards in the file and press Ctrl+A. As you can see the selected area does not match the selected artboard as should be the case. Also choose the Flood Select (Wand) tool and with one of the layers in one of the artboards active, click in the empty area inside that artboard. As you can see, the selection area goes beyond the borders of the artboard, in fact up to the origin point of the document. AFPhoto Artboards.afphoto
  9. When working with documents that have multiple artboards in AF Photo some problems arise: Drawing outside of the artboard is possible, which does not feel intentional (as opposed to preserving pixel data when moving or scaling it outside of the bounds of the artboard, that works as expected). Selecting via Ctrl+A or the Wand tool only works as long as the artboard was not moved from it's automatically generated initial position. When Moved away from that initial position only the parts that still overlap with the initial artboard bounds are selected. There might be more problems I'm not aware of but these are the ones I stumbled over.
  10. I understand that hiding a layer does not lock it from being transformed, makes total sense to me, since it does happen from time to time that you would move a bunch of layers, or scale them etc. and do want the same transforms on (temporally) hidden layers. What I really don't understand however is in which case drawing or erasing on a hidden layer would be desirable. I honestly cannot think of a situation where someone would want that (though that ofc doesn't mean nobody else could. So please let me know if I'm missing something here ). Therefore I still think an option to change that behavior might be a good idea? Or as I said, maybe at least a warning when trying to draw or erase on a hidden layer.
  11. In Affinity Photo it is possible to manipulate hidden layers, for example drawing on them with the brush tool or erasing with the eraser tool, which should not be possible (at least without a warning).
  12. The Flood Select tool apparently does not work on Image layers. Works fine on pixel layers but not on image layers which is pretty inconvenient. And I'm not talking about editing or drawing on the Image layer, but only selecting the desired parts of it with the Flood Select tool to for example make a mask from that selection or paint inside the selection on another layer to name just two cases where it would be helpful.
  • 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.