Ben

Every time Tony is asked this question, the answer seems to double. Last I heard it was in the millions (dollars, sterling; doesn't much matter). The problems are the variety of GUIs on Linux, and the need to support it for years after the initial work is done. We are already planning for three platforms, Mac OS, iOS, and Windows, and we don't want to be overstretched.

Sometimes you want to also know what it is you are snapping to.  Yes, we could just change the cursor (which we'd have to do for *every* tool that employs snapping), but you'd lose the indication of what was snapped.  As far as I gather, people generally find all the other snapping indicators useful, and certainly important for showing things such as edge alignment where there is some distance between objects.
 
My initial plan is to try create a localised highlight (a circle of 30 pixels or so) around the actual snap points where a geometry snap is made.  That might make things neater.

Sometimes you want to also know what it is you are snapping to.  Yes, we could just change the cursor (which we'd have to do for *every* tool that employs snapping), but you'd lose the indication of what was snapped.  As far as I gather, people generally find all the other snapping indicators useful, and certainly important for showing things such as edge alignment where there is some distance between objects.
 
My initial plan is to try create a localised highlight (a circle of 30 pixels or so) around the actual snap points where a geometry snap is made.  That might make things neater.

We are going to look at smart objects at a later date.  The solution will be quite involved, and whatever we do will need to fit with any solution we come up with for linked documents.

Before I added the other method, we had Space doing the wrong thing from the menu (it was doing what Distribute does).  It's now consistent with the alignment panel.  I added the two variations because they are both useful in different situations.

We don't do it yet, but it is on our list of things to look into.

Bootstrap style grids will be addressed when we improve guides.  This will include automatic guide creation tools.

This is already on my to-do list.  I'd already got a plan for a Grid widget that works along snapping.  This will include a way to move the grid origin.

Bootstrap style grids will be addressed when we improve guides.  This will include automatic guide creation tools.

This is already on my to-do list.  I'd already got a plan for a Grid widget that works along snapping.  This will include a way to move the grid origin.

Before I added the other method, we had Space doing the wrong thing from the menu (it was doing what Distribute does).  It's now consistent with the alignment panel.  I added the two variations because they are both useful in different situations.

This is already on my to-do list.  I'd already got a plan for a Grid widget that works along snapping.  This will include a way to move the grid origin.

Bootstrap style grids will be addressed when we improve guides.  This will include automatic guide creation tools.

If I understand this step correctly, it is the same as AD's method, except that you have to release the mouse button for the Control (Command on a Mac) key to switch the cursor to the node tool, & then click again on the node to move it, right?
 
AD's method requires that extra click, but it allows you to do anything the node tool can do to, including modifying or deleting bezier control handles, including the one from the previous node. It also allows you to grab the line segment between the previous & current node & move it, affecting both nodes bezier control handles.
 
That is a lot of functionality, none of which I would want to give up for a simpler control key move node feature.

Distribute sets an even distance between the centre points of the selected objects and Space sets an equal distance between the edges of the selected objects.

Yes - I've thought about renaming that to "Export checked" or something similar.

Yes - I've thought about renaming that to "Export checked" or something similar.

krollian,
 
I agree, plus everyone has a different reason for using the app. I am mostly interested in illustration, not so much UI or layout type work so I gravitate to those features that tick the boxes I'm interested in...  The important thing I see and what makes Serif a little different than most, is that the guys and gals doing the hard work are listening to their users and creating something that ticks their boxes as well, creating something that is more than the sum of it's parts.  :)

It's already on the list for future improvements.  Unfortunately, it requires a substation change to our tool framework, so will take some time.

It's already on the list for future improvements.  Unfortunately, it requires a substation change to our tool framework, so will take some time.

At some point in the future I'll be adding 'live' corners to shapes so that you can corner without having to convert to curves.

Just to add a tiny bit to what MBd already said for newcomers here: if you have used other software makers' support sites for help with their products, prepare to be blown away by how much better the support you can get here from the Affinity team is than anything else you likely have seen from anybody else.
 
Here, you won't find any of those annoying scripted "boilerplate" answers that are not relevant to whatever you ask about & make you wonder about the support person's reading comprehension skills.
 
This is support done right!

You're right - this probably needs to be looked at.

It's definitely the worst part of my day.  ;)

The problem is that the rules are very complicated.  Depending on the PSD export setting for "edibility" or "accuracy" different layers will get rasterised.  Masking, transparency, blend modes and layer effects also determine whether we need to rasterise as PSD cannot handle certain masking structures.
 
In short, it'd be very difficult to document the rules as it'd be more of a (very large) flow chart.  I also tweak them as I find new examples that could be exported better, so they aren't even set in stone.  The short of it is, they are geared up to try provide the best export we can achieve.
 
As MEB says, in the future I would like to add some sort of visual feedback for PSD import and export, so you can see how you document structure is affected.  I cannot give any idea when that might be.  For now, you'll just have to compare the results and see what happens.