Jump to content

lepr

Members
  • Posts

    6,163
  • Joined

Everything posted by lepr

  1. The right hand end of the context toolbar of Pen Tool has toggles for 'use line style' and 'use fill'. If you see a pair of chevrons at the end of the bar then there are more controls which become available by clicking on the chevrons.
  2. It is a bug since way back in v1, and there is a workaround. The bug is that transparency in an object's FX Gradient Overlay incorrectly affects transparency of the object, instead of just the overlay, if the object is clip-nested in some other object. An Artboard is a clipping object, therefore its content is subject to the bug. Fortunately, there is a workaround which tricks a correct rendering without requiring a change to the structure of the document: add an invisible opaque FX Colour Overlay to the object that has transparency in its FX Gradient Overlay. An invisible opaque FX Colour Overlay can be achieved by black with blending mode Add, or white with blending mode Multiply.
  3. There seems to be a misunderstanding about the problem. Auto-select options do not help. There is a regression in 2.6.0: https://forum.affinity.serif.com/index.php?/search/&tags=AF-5999
  4. Sorry, I missed the bit where you said it works on your Mac.
  5. The technique you tried in your video works correctly on my Mac. You shouldn't need to use the more complicated method shown by Bruce.
  6. Yes, I get the impression James Ritson got the job.
  7. Yes, clearly, and that is why I said it's possible that Serif is not an attractive employer.
  8. It's been like that since v1, and I suspect it will be classed as "by design". A workaround is to enclose the aliased object in a Group then rasterise the Group.
  9. The solution would be the developers restoring the previous behaviour. Hopefully the bug will be acknowledged by a member of staff today.
  10. There was a recruitment ad several months ago. It’s possible that Serif (Canva Nottingham might be more appropriate now) is not an attractive employer.
  11. Certainly not universally true. Rasterisation of vector objects can be avoided in the cases of FX Outer Shadow and FX Outer Glow.
  12. A Constraints Group really is a vector Rectangle with no stroke and no fill (although it can be given a stroke and/or fill after being created). A particular problem with the implementation is that it can crop off part of the stroke of a child object and then workarounds have to be contrived.
  13. I would describe the rasterisation of your Group as a bug. There is a workaround: instead of the FX being on a Group which contains various objects, put the FX on an invisible Rectangle which contains these objects. (My "invisible Rectangle" is a vector Rectangle with no fill and no stroke.) Try to export to PDF edited.afdesign Try to export to PDF edited.pdf
  14. Exactly the same for me. 2.4.2 is needed for good stroke expansion.
  15. The new behaviour is in the last beta too. I didn't have FPA enabled when testing for it before, so it didn't affect me. Normally I opt+drag an object or use Duplicate command to duplicate an object, anyway, and so there was little chance of seeing the new behaviour until reading about it. For a pasted non-rotated/skewed object with stroke, it seems to be the top left corner of the bounding box that would contain the expanded stroke that gets aligned with the pixel grid.
  16. I hadn’t seen that thread, but I’ll test the various scenarios described there when back at the Mac.
  17. I’m not relying on my eye. I have 6 decimal places for pixel measurements and there is zero movement of the pasted object in beta 2.6.0 on my Mac. Edit: now I realise that the movement does happen when Force Pixel Alignment is enabled.
  18. Not at all. I've slightly re-worded my comment because it was ambiguous. The bug is not in the last beta of 2.6.0. It is new in the retail release of 2.6.0.
  19. Wow! I am not seeing that bug in the last beta of 2.6. A familiar story in Affinityland. Ah, I did not have Force Pixel Alignment enabled. Now I see the new behaviour is in beta 2.6.0 (3134).
  20. Yes, the workaround only works correctly when the scene behind the group is opaque across the entire canvas.
  21. A vector/text object with FX Outer Glow or FX Outer Shadow can be exported with the object remaining as vector/text over rasterised effects, depending on the PDF options. However, a bug results in the exported FX always being given Normal blend mode even when the PDF version supports alternative modes that may have been specified in the Affinity document.
  22. Not exactly. When the Passthrough Group contains a mix of Filters/Adjustments and non-Filters/Adjustments, the blending is still Passthrough for the non-Filters/Adjustments, but the Filters/Adjustments affect only the objects inside the Group. It is the Passthrough still functioning for the non-Filters/Adjustments which made me realise my workaround for making the Filters/Adjustments affect the scene behind the Group in addition to objects inside the Group. The workaround is to put a white object with Multiply blend mode at the bottom of the stack inside the Passthrough Group. That object can be a Fill Layer in Photo, and a good alternative in Designer is a vector Rectangle covering the canvas (and bleed if appropriate).
  23. Both scenarios are replicable on my Mac. It seems that if an entity (a Layer or object) is selected, then the tool's width field and the Stroke panel both display the stroke width of the entity rather than the width that will be drawn. In contrast, older versions of the tool showed the width that will be drawn, and the Stroke panel showed the width of the currently selected entity.
  24. Welcome to the Affinity forums Affinity's equivalent auto-scaling feature is Picture Frame, but that's currently only available in Publisher.
×
×
  • 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.