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

lepr

Members
  • Posts

    5,585
  • Joined

Posts posted by lepr

  1. 10 hours ago, dantaylr said:

    So the real bug is that when you expand a stroke at a small size, some points may be merged into each other causing unintended side effects

    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. 24 minutes ago, Pšenda said:

    From the sentence "This has eluded me since Affinity launched.", I conclude that the OP especially appreciates the information about the use of the Point Transform tool and its existence in ADesigner (the tool is not immediately visible in the Tool panel - it is shared with the Node Tool, so it can be easily overlooked).

    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. 11 hours ago, Bryan Rieger said:

    It gets harder to not only see the 'close loop', but to also trigger the auto-close feature the more you zoom in.

    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. 37 minutes ago, thomaso said:

    Isn't it rather due to the hybrid nature of "text" objects where a fill colour 'usually' affects the containing text (not the shape of its frame), and so do layer effects – unless the text frame gets a fill colour assigned?

    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.

  5. 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.)

  6. @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.

  7. 7 hours ago, Thomahawk said:

    select them all. Suddenly rounded corner option not to be found anymore.

    7 hours ago, Thomahawk said:

    I have to go back to step one, rounding the first rectangle, and make the copies and placements afterwards.

     

    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.

  8. 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.)

     

     

     

     

×
×
  • 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.