Jump to content
You must now use your email address to sign in [click for more info] ×

lepr

Members
  • Posts

    5,554
  • Joined

Everything posted by lepr

  1. Yes, an old Affinity problem. If I remember correctly, good stroke expansion in Affinity requires the distance between nodes to be a minimum of 0.5 document pixels. (Affinity's internal unit of measure is pixel.) You can either temporarily scale up the object in order to do the expansion, or you can temporarily increase the document pixel density (termed DPI in the document properties) in order to do the expansion.
  2. To me, the sentence seemed to refer to the elusive ability to snap an edge of one object to any edge of another object rather than an object's bounding box.
  3. The feature seems to be working 'by design', as Serif would say. The auto-close threshold is a constant distance in screen space rather than document space, and so it becomes smaller in relation to the object's displayed size as the zoom increases. Notice that the red loop symbol is about the same length as the pencil pointer at the moment it first appears, regardless of zoom. The 'harder to see' is simply the poor contrast of red on the black of the stroke. As you zoom in, the black becomes more expansive until the red loop is never being presented on white.
  4. Note that my somehow unhelpful video showed exactly the same technique but done with Move Tool which is available in all Affinity apps.
  5. Yes, I should have added that. PTT is actually one of my favourite tools in Affinity.
  6. There is a way with the Move Tool. An object's Transform Origin can be used as a handle. Snap it to the object's path and then use it as a handle for dragging the object until it snaps to another object's path. snapping.mp4
  7. That's correct when a document isn't 32 bits per channel. I thought it unlikely your documents would be 32 bpc, but it was a possibility, hence my advice regarding the panel.
  8. If your Affinity documents are 32 bits per channel, ensure ICC Display Transform is enabled in the 32-bit Preview panel.
  9. Affinity internally uses pixel as its unit of measure. The maximum corner radius seems to be 1991.1 px, and that is equivalent to 168.6 mm when PPI is 300.
  10. Welcome to the Affinity forums Please attach an Affinity file (.afdesign, .afphoto or .afpub) which has the problem.
  11. I was referring to any object with an outside-aligned FX Outline. The object is composited over an outline-coloured dilated silhouette of the object. Reducing the opacity of the object's fill colour results in the fill being blended with the silhouette instead of concealing the silhouette.
  12. The behaviour in the OP's video is the "by design" (as Serif would say) result of the implementation of FX Outline.
  13. The black gradually becoming revealed as the white fill colour gradually reduces in opacity is coming from a Layer Effect Outline (there are two of these on the object). Instead of reducing the opacity of the fill colour, use the control labelled with "Fill Opacity" in the Quick FX panel or Layer Effects window or Blend Options window to reduce the opacity of the fill without revealing an FX Outline colour. (By the way, the Appearance panel in AD and the Designer persona of APub allows multiple strokes to be given to an object.)
  14. @DarkClown Seems like the Auto-select is in Object mode despite saying Default in the context toolbar, and so your marquee selection is drilling down through Groups to directly grab the objects within the Groups - notice how a Group is only dimly highlighted in Layers panel when its content rather than itself is selected. Performing a deletion of the contained objects leaves the now-empty Groups in the document. I have had the Auto-select behave contrary to its stated mode a few times and corrected it by toggling to another mode then back to the desired mode.
  15. If you read carefully, my first suggestion in this thread (back in 2020) was exactly that - opt/alt-click a handle.
  16. I'm not sure if it's what you want, but opt/alt-click the Node Tool on a segment, rather than a node or handle, to completely straighten that segment.
  17. In that case, the functionality could have been kept and the name changed to Rectangular Brush.
  18. In the file Z50_1657.afphoto, the Pixel object isn't truly opaque except near the top. Make it all fully opaque then do Rasterise & Trim, and then you'll be able to add the correct FX Outline. There are many ways to make the Pixel object fully opaque, so let me know if you need advice about that.
  19. No you do not need to "go back to step one". A selection of multiple Rectangle objects can have their corners changed simultaneously when any shape tool or the Node Tool, rather than the Move Tool, is active.
  20. Divide does not work correctly when there is no operand that only partially overlaps another. A workaround is to include a pair of additional temporary operands that do only partially overlap, do the Divide, and then delete the fragments of the temporary objects. See example below. (Other workarounds using other commands or tools exist, but I'm showing one for when you do want to use the Divide command in particular.) divide workaround.mp4
  21. That conversion of vector to raster can be avoided by using the highlighted option in the screenshot below. Instead, a mask will be nested inside the vector object and the Erase Brush will modify the mask.
  22. thomaso shows the extra info that I wrongly assumed would be too obvious to require mentioning
  23. Power Duplicate will scale the size of text in Art Text but not Frame Text, Shape Text and Path Text (despite the Art Text Tool being used to create Path Text). Workaround: apply Convert To Curves command to the Path Text before doing the scaling power duplicating.
×
×
  • Create New...

Important Information

Terms of Use | 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.