Jump to content

simonlayfield

Members
  • Content count

    28
  • Joined

  • Last visited

1 Follower

About simonlayfield

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Ah. I'm still using v1.61 via the App Store so perhaps this is something that has been addressed already. Interestingly (shown bleow) if you drag an existing symbol inside another it doesn't appear in the instances (as I mentioned previously) BUT if you drag the (nested) symbol in to a new layer and THEN nest it, it works! So this is an easy enough workaround, if others are struggling with the same behaviour. Thanks!
  2. Hey all, I'm having an issue with symbols again so I thought I'd raise it here in case for some reason it's expected behaviour. So, I'm using symbols functionality to create a tiled patterm - this way I can update or add to an existing symbol and the tiled pattern as a whole updates (this is for textiles so by far the most efficient method). Unfortunately it seems that using symbols within symbols isn't an option. As you can see in the capture below dragging regular curves in to the tile symbol updates the pattern - but dragging a symbol in to an existing symbol doesn't update the instances. Is this as expected? Thanks in advance
  3. simonlayfield

    Affinity Designer curves disappear when using Union tool

    Y'know what? Clicking Close Curve twice actually seems to fix it. Is this expected? Does closing a curve twice in some way change it's behaviour/curve properties?
  4. simonlayfield

    Affinity Designer curves disappear when using Union tool

    Sure no problem! I've reduced the file down to just the elements that are causing the issue. In the file there are a number of groups (flowers). If you Ungroup all, select Close Curve (so that all curves are closed and can be merged together as shapes) then hit Add you'll see some of the petals disappear. affinity-union-bug.afdesign
  5. Hey team, Couldn't find this on the forum but unsure if it's a bug or expected behaviour due to the complexity of the curves. I have a number of unclosed curves drawn using the vector brush tool. I need to be able to close the curves and combine them in to one curve so that I can use them as a mask for another layer. Closing the curves seems fine, but then unfortunately when using the Union tool some of the curves disappear. Is there a reason as to why this might be? See below Thanks
  6. simonlayfield

    Add Pantone colors in Affinity Designer

    I needed the Pantone Fashion and Interiors colour book available in Affinity Designer for designing tech packs for the clothing industry. I started out by selecting from the whole spectrum of colours (colour wheel) and then had to go through the document at various stages, copying hex codes and using the Pantone Colour Finder to provide me with the closest Pantone colour, copying the hex code and pasting it back in to the hex field in AD. So...a bit tedious, not to mention a little unreliable because when converting any old hex colours to Pantones the results aren't as close as I'd like. However, I did find a list of Fashion and Interior Pantones hex codes online here and reformatted the pantone-numbers.json to csv. That way I can drop them in to Affinity Designer > Contents > Resources > pantones and they show up as an additional palette in AD. Much easier. It's attached here if anyone needs it. Hopefully there isn't a downside to this, other than the colours themselves needing to be manually updated when Pantone update their range. pantone-fashion-interiors.csv
  7. simonlayfield

    Node Tool Curve Selection Accuracy

    @MEB Ah I see, thanks. Yeah this does help. Also dotted line problem solved - thanks!
  8. simonlayfield

    Node Tool Curve Selection Accuracy

    @fde101 I do find naming layers, groups and curves useful in certain cases. In this case, though, sorting and naming 80 grid lines isn't what you'd call a sustainable workflow. For example, what would be the best way to name these grid-style lines? horizontal 1, horizintal 2, horizontal 3...? I that case if I decide to add more lines in between later then these numbers become semantically incorrect and misleading. I appreciate that some manual management of layer/curve naming can help in some way with navigating the elements, but it's kind of sidestepping the issue that curves should probably be directly selectable in this instance - if not by default then perhaps a setting that can be toggled. That's my POV, but I do appreciate your suggestion and agree that it is helpful - just not ideal.
  9. simonlayfield

    Node Tool Curve Selection Accuracy

    Also on a separate note - can you try creating a simple dashed line in this document? It doesn't seem to work at all for me. If this is a bug I'm happy to create another ticket but thought I'd check first. Thanks
  10. simonlayfield

    Node Tool Curve Selection Accuracy

    @Sean P Sure thing! file attached. The issue isn't that the lines aren't at all selectable, it's that the Node Selection tool presumably isn't designed to select lines (curves) directly. So when you have lines close enough together it seems to prioritise the selection of lines that are higher in the layer order (perhaps this also involves the curve's boundary box). Try clicking directly on a line in the roof in the attached file and you'll see what I mean. It might be that when you zoom in close enough you can directly select a curve but it's unreasonable to suggest that this is a manageable workflow when numerous adjustments may need to be made, and despite zooming in to select you'd only have to zoom out again to see the context of your change. @fde101 While you're right that you can select the curve in the layers panel, it's in no way easier. When dealing with lines like this, all part of the same section of artwork (and so alongside each other in the layers panel) this is what you see: ^ In this case there are about 80 curves - all indestinguishable from one another in the layers panel. It's like bobbing for apples, essentially. church-sketch.afdesign
  11. Apologies, I think I may have caused the global colour confusion by suggesting it in a previous comment. I did stress that this only satisfies the single use case of changing the colour of multiple objects (fill/stroke) without having to selecting them - something that if you weren't aware of might save you some time. In hindsight perhaps I shouldn't have muddied the thread topic. My bad.
  12. I searched the forums but couldn't see this issue (or at least how to work around it) so apologies if this is a duplicate. I have a grid of curves (lines) and need to select one line in particular, but unfortunately the node tool struggles to identify the curve I'm attempting to select (the vertical line): Is there a way that the Node tool can explicitly select the curve I'm actually clicking on and not curves in the surrounding space? My guess is the node tool is selecting the other curves based on their boundary boxes - which being higher in the layer stack take priority. Either way it's super fiddly to deal with when adjusting each curve in the grid by having to move the layer order around every few seconds. Or am I going the wrong way about this? Thanks in advance
  13. Just chiming in to say this happens to me sometimes too and is pretty painful when I have a large number of symbol instances. What might solve the problem is that when working with Symbols and performing an action that breaks a synced attibute a brief UI prompt to say: 'Performing this action will affect the synced attribute of this symbol.....[Continue] or [Cancel]'. This way at least the user is aware that a Symbol will break as a result of the action and can decide accordingly.
  14. @VectorVonDoom It's true - and I wasn't suggesting this is a sufficient replacement for that feature. Select by same colour/fill/stroke appearance is powerful because it allows you to perform number of options once selected. I thought it was worth posting because it covers one of the many use cases that might apply, and global colours are a feature perhaps not everyone would know about. I'm hanging out for the feature requested in this thread because I've felt the pain of having to select a crazy number of shapes and curves in order to make document-wide amends to complex artwork. Yeah, this involves some manual management of global colours. If it helps, you can show global colours as a list and then rename them to more useful/descriptive terms. See below: The only caveat here is that if you end up using the 'Face Tone Dark' global colour for something that isn't part of the face then semantically it can get confusing. It really depends on the complexity and level of granular control as to what naming system is most useful.
  15. @madtho If you happen to be creating a project from scratch you can workaround having to change colours in multiple places by using global colours within a Document Palette. If, when creating new objects the global colour swatch is used as a fill or stroke colour then you can change this colour later and it will update whereve it is being used in the document. See below: The only thing to be aware of is that a global colour isn't a global colour in the strictest sense - the swatch actually has to be active when you're creating new objects. It will, however remain 'attached' to the object if a shape is duplicated (as above). Of course this isn't the same as selecting by same fill/stroke/appearance but as far as amending colours in a document goes it saves having to essentially go through the same manual process of selecting a huge number of shapes and curves (which would have to be selected separately by whether the colour of the stroke or fill needed changing). Hope this helps
×