Jump to content


  • Content Count

  • Joined

  • Last visited

  1. That's not exactly what I meant - I realise updating documents in-situ would be virtually impossible. What I meant is an application palette where any document referencing that palette would be updated on the fly when it's opened (as if you had just updated the palette with the document open).
  2. Thanks - I think that will do the trick. It would be nice if there was an automated way to pair existing objects with the global palette where the colours match (which is true in every case for us - the build process will fail with an error if we get it wrong). But at least we'll only have to do it once. It seems as if global palettes are document-specific. If you want it in other documents, you need to export/import. Is there a way to make an Application palette that is also global so we could update all the documents in one step if the colours change?
  3. Apologies if there is a solution to this - I've searched and experimented, but can't find a good answer. I need to maintain thousands of UI icons for a wide range of different (but related) products. They are all required to use a strict colour set, but periodically the prescribed set changes, e.g. to accommodate dark mode better. When this happens, it necessitates a really boring process of working through every image one-by-one and replacing the colours as required. It would be brilliant if there was a quick way to manage this in Designer, e.g.: Capture a style that is just colour, and have everything drawn instantly update as the styles are edited Have some kind of find-and-replace that worked on colour (or other attributes) Does anyone have a suggestion for a good workflow to solve this? Or is there anything planned for the future that might help?
  4. We've had an employee working remotely using Affinity Designer as a demo on Windows to see if it served their needs. Having confirmed that it did, we bought a licence code and forwarded it to them. They've reported that Affinity Designer just says the demo has expired and doesn't prompt for a licence code. Do we need to uninstall and reinstall, or can I suggest some other method?
  5. I joined the forum back in 2014 when I first purchased Affinity Designer. I posted about the lack of arrowheads back then. The universal response was, "they're on the roadmap - coming soon". I've been eagerly jumping onto every release for the following 4 years searching for arrowheads…
  6. Yep, likewise. I was surprised/disappointed to find this lacking in Designer when I first bought it. When every application of this type – from the most expensive commercial package to the lowest 'hobbiest' offering – has arrowheads, I simply assumed it was there. But I was encouraged to see it on the Roadmap from as far back as 2014 and assurances that this was definitely coming. This isn't a complex feature to add – why the huge delay? I feel really embarrassed about promoting Designer when something so basic is missing.
  7. +1. I'm struggling with this too. Having to constantly flick between personas to check the relationship between illustrations and slice boundaries is a painful workflow. Really easy for someone to make a mistake too.
  8. Here's a sample… CT_OBJ_Timber_Cambered_140x194.svg
  9. I need to edit some images that were previously created in AI and exported as SVG. They look fine when opened in Designer except for point objects in the image, i.e. a single dot or zero-length line. Here's a sample from the SVG: <line id="Dimension_B___x28_Dash_x29__86_" class="st20" x1="71.5" y1="40.5" x2="71.5" y2="40.5"/> They exist in Designer but cannot be seen or made visible. Modifying colour, stroke width etc has no effect. The points render correctly in other software (including the Finder preview). Is there some way to make them work properly in Designer? [Note that I'm not looking for another way to make something that looks the same. I have hundreds of images to edit, and I can't afford to have to replace every instance of these points with something else]
  10. Yes, I think that's exactly what I'm looking for. To quote the reply: I'd add a suggestion that the mask should apply to the whole style category rather than individual styles. I'd envisage creating categories specifically to capture "Arrowheads" and "Linestyles" (dashes), and it will make the styles easier to capture if I know (for example) that I can capture just the arrowhead by capturing a style in the "Arrowheads" category. That would make for a great workflow.
  11. I was pleased to see that a path can be dashed in a recent release of AD – it's an omission that has been holding me back from using the software on a regular basis. But the implementation is so weak, it's almost unusable. I find most of AD has some really well thought-out workflows, but in this case workflow has been overlooked. For people who use dashes, a degree of uniformity is important. A dash is defined for a specific purpose, and needs to be distinct from dashes made for other purposes, e.g. the dash for a grid-line might look completely different to a dash for a hidden feature. You will be often in the position of wanting to store and recall a dash style independent of all other path characteristics, e.g. line weight, colour, fill pattern etc. AD doesn't seen to have any way to capture a dash style other than to create a 'Style' that captures all other attributes. So attempting to capture a dash from one shape and apply it to another will also change the line weight, colours, fill etc. Can we have a way to store, name, and apply just the dash style? And likewise for arrowheads when that feature is implemented. The features are otherwise not very useful.
  12. +1 for arrowheads. I've never encountered illustrative software that doesn't support them – it's essential for people in a wide variety of fields, e.g. architecture, engineering, science, maths etc. I'd use AD for everything, but the lack of arrowheads and a poor implementation of dashed lines forces me elsewhere all the time. It's a shame, because AD otherwise has great tools and sensible workflow. And please don't repeat the mistake you've made with dashes. We need to make collections of both dashes and arrows that can be independently applied to different sets of paths. Styles in AD grab everything – line weight, colours, fills etc. I frequently need to change just one thing in a selection, e.g. the dash or the arrowhead, but I don't want all the other properties to change too. And trying to replicate the same dash/arrow manually over and over is a really bad workflow. Please allow the user to capture and reuse a dash or arrowhead independent of other style characteristics.
  13. That's good news about dashed lines. I'd like to know there is a definite plan for arrows too - it's an odd omission. I've used many illustrative applications, and never come across one that had no arrow facility. Essential requirements are that: 1) Different arrows can be independently specified for the start and end of a path (including none for either); 2) The arrow size is user-defined, i.e. it isn't inferred by the line weight; 3) Arrows are automatically orientated at a tangent to the start/end of curved paths. Options that would make it really outstanding would be that: 1) The weight of the arrows can be different to the path, e.g. a 1pt arrow at the end of a 0.25pt line; 2) The arrow size can scale with the object (as you can already do with the path weight). If arrows and dashes are added, we would transition to using Affinity for most of our illustrative work. We really like the workflow, uncluttered UI and rendering.
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.