rubs

This is a really annoying bug. Will you fix this for the next beta? Please?

I think using the selection color and line styles (or other visual indicators in the selection) would be great for this and other uses. See here for a related idea concerning using the selection color for symbols:

In the latest beta (I never noticed it before), pressing Esc in the Text Height field in the context toolbar does not take you back to the working area. The control goes blank instead. Pressing Esc again brings the current value back, and so on. Please take a look at this -- thanks.
 

BTW, I wonder why the Align drop-down has the Done / Cancel buttons. They seem a bit old-fashioned compared to the other tools. Undo works perfectly in AD, so I think they may well be removed.

Hi, it seems that Affinity Designer lost its ability to copy objects as vectors into the Windows clipboard. I'm testing it using several target softwares (CorelDRAW, Xara Designer, Inkscape, etc.) and all I get are DIBs / bitmaps. In Xara it's even worse because all bitmaps are blank.
 
Also the 'Copy items as SVG' option in the Preferences dialog does not change anything for me.
 
Any thoughts?

Hi MEB, as a working professional illustrator and someone who has been in the Affinity camp for some time now I can't overstate how eager I am to seeing as many of these roadmap items brought on stream sooner than later. :-)  Having said that, yours is a small team and each one of these roadmap items need to be implemented in to the big picture smoothly and with much care and thought. That goes without saying and I don't think anyone would disagree with that reasoning.
 
Might I suggest as a way to smooth the transition or perhaps help ease frustration as you develop these items, Affinity might think of launching some sort of dedicated weekly or monthly status update on all things Affinity - what's going on, what's nearing completion, what's coming up, etc... similar to the pdf magazine you did a while back but way less polished, maybe more of an email subscribed bulletin or something similar. It might help both you guys control the flow and nature of information you release and help us users feel a bit more connected to all of the cool stuff that's happening at Affinity HQ, building excitement at the same time. Just a suggestion. :-)

Yep. I believe the betas exist for refining and bug fixing, so I'm pretty confident there will be room for improvement. I'm just reminding the nice guys at Serif (again) that they first need to get their current features working before they implement new ones. There is a overwhelming amount of known bugs, serious flaws and performance problems in 1.6. Some of them were even introduced quite recently and are still not fixed to date.

Yep. I believe the betas exist for refining and bug fixing, so I'm pretty confident there will be room for improvement. I'm just reminding the nice guys at Serif (again) that they first need to get their current features working before they implement new ones. There is a overwhelming amount of known bugs, serious flaws and performance problems in 1.6. Some of them were even introduced quite recently and are still not fixed to date.

Ben, I believe all these new implementations are quite exciting and I really look forward to see them working. But my main concern is with all the functionality in Designer that does not work as it should. I'm referring especially to the many bugs with constraints, symbols, artboards, exports and others, as well as some really bad performance bottlenecks. I wonder if these pending issues will still be present in version 1.7, or you guys do intend to fix them in the near future.
 
Will you or anyone else from Serif be able to answer this?
 
Thanks in advance, and sorry for being a pain 

The workaround I use is to first manually remove all constraints from the desired objects and restore the x-y arrows in the Constraints panel, then group them. It's time consuming, I know, but I hope it works for you.
 
Alas. I still wonder why there are no responses from Serif for well over one year now. This is just one of a collection of very nasty bugs with constraints, objects and artboards that were never addressed.

It's a balance between "accelerating workflow" for infrequent tasks, and adding UI clutter that the majority of people will never use.  Currently, a lot can be achieved by putting formulae/expressions into a lot of the edit boxes on the transform panel and other places.  Adding another box on a panel will only be a shortcut to doing exactly the same task.
 
I've worked a lot on our expression parser, and added a lot more capabilities to it.  Currently this is a big work in progress, and I'm holding it back from 1.7 until I'm happy with it.  I'd also like to add some more involved UI for showing what the expressions can do, such as a function list, and some form of presets - though this is still very much in the concept stage.

Here's an example. When making a donut chart composed of two colored sections, you may:
 
1) Create two identical donuts, one of each color.
2) Adjust donut #1's angle to something other than a multiple of 90°.
3) Adjust donut #2 so its start angle is the same as the end angle of donut #1. This is currently only possible by typing the same values.
4) Adjust one hole radius to something other than a multiple of 25%.
5) Adjust donut #2's radius to match #1's. Currently you have to type the same value.
 
Snapping the control points just like nodes do would be tremendously helpful in steps 3 and 5 (specially considering this can already be done with the node tool itself).

Here's an example. When making a donut chart composed of two colored sections, you may:
 
1) Create two identical donuts, one of each color.
2) Adjust donut #1's angle to something other than a multiple of 90°.
3) Adjust donut #2 so its start angle is the same as the end angle of donut #1. This is currently only possible by typing the same values.
4) Adjust one hole radius to something other than a multiple of 25%.
5) Adjust donut #2's radius to match #1's. Currently you have to type the same value.
 
Snapping the control points just like nodes do would be tremendously helpful in steps 3 and 5 (specially considering this can already be done with the node tool itself).

What about snapping to other shape "geometry" and "key points"?

It's not a bug - it's just an inconsistency, but not necessarily an overlooked one.  The two tools in question have fundamental differences - the Move tool will only ever show the nine handles for the selection box, whereas the Node tool could end up displaying hundreds of handles.   So, the hit tolerances have largely been arrived at as a result of trying to balance this.
 
You should also take note that the Move tool has special nested handles.  The handle you were picking up at 16 pixels is used for rotation.  If you move a little closer to the centre, you'll notice that the cursor changes and it provides scaling instead.  The scaling handle size is closer to the size of the Node tool handles (so more consistent with our standard handle sizes).
 
The various tools have their own hit testing code for various components. There is the preference for Tool Handle sizes which acts as a scaling to the standard size handle for each tool, but each tool will not necessarily have the same standard size handles.  There is probably room for us to revisit how this all works, and standardise it better across all tools.  I've been working on a lot of tool changes for 1.7, and there could be room to deal with it as part of these changes.

Is it possible to get a second antialiasing option which would get rid of the gaps between vectors that aren't actually there?

Symbols (along with slices, artboards and constraints ) still are one of those problem areas in AD. Two possibly related problems that I've listed:
When copying and pasting layers between artboards where some layers are symbols, the original layers frequently get out of order and one of them becomes the bottommost layer in all artboards. The Exclude from Snapping command does not propagate to all symbol instances.

But there will be in 1.7.  Already done.
 

Serif have obviously done the arithmetic and come to the conclusion that they can do exactly that. If they're able to sell (say) half a million copies at 50 bucks apiece, they'd be crazy to double the price and risk only being able to sell a fifth as many copies.
 

Our ability to produce professional software is somewhat governed by income from those products. Income for us is calculated by copies x price and our current price point is simply designed to produce the greatest income. Increasing the cost of the product will not increase our ability to make competitive PRO software.

Oh, for God's sake: No two versions please!

TOTALLY AGREE!!!!!!

And that is great. I love the way Serif is innovating. But on the other hand, you don't have to invent the wheel twice. If there is something that is working allready really well, you just could implement that.
 
That is what most people are trying to say here, I think.
 
They say: look at other program's tools wich work really well and people love, implement those and keep on innovating and put new tools in other programs lack, this way you get best of both worlds; tools that are familiar to most and work well and new tools only Serif can offer. This makes for a well designed user friendly program wich is still unique.
 
On the other hand, people must realise that you just can't copy other program's tools....and therefor have to re-invent the tool to be able to implement into your own program.

Wow @Ben, I've just downloaded and watched all the clips with the new features. Well, I'm an UX designer and I've been working a lot with icon design lately, so what got me excited about these new features are all the snapping options for the node tool. REALLY AWESOME.
 
I'm not sure if this should be posted in this topic, but since it's related to shape manipulation, I was wondering if would it be in your roadmap a set of features to resize shapes with keyboard shortcuts. Similar to what Sketch does:
cmd+right arrow to increase width by 1px cmd+left arrow to decrease width by 1px cmd+shift+right arrow to increase by 10px (or specified amount in settings) cmd+shift+left arrow to decrease by 10px (or specified amount in settings) Also, differently from what Sketch does, we could benefit from the object origin (pivot), so object could shrink or grow from an specific point relative to the shape, instead of just from top left corner.
 
Congratulations for the awesome work!
 

I better hope "childish" is meant as a compliment here, standing for "nice looking and easy to use" ... otherwise read this:
Seriously? You are working in graphics / design and don't like a colourful and fun, light looking user interface?
I appreciate every bit of colour, fun and lightness I can get in my life ... and when this colour is part of an awesome software I use every day, even better!