robinp

I came here to check before buying v2. I honestly cannot believe they haven’t fixed this. Astonishing. 

Except Designer was launched in 2014. On this basis criticism is never logical because there is always potential for an updated version.

I really like Affinity apps.
But whenever I use them I feel like I’m constantly being tricked / trapped by them. 

I work on a file then save or export and the location inexplicably defaults to the last location of save or export, not the location of the currently open file.
It’s a topic that’s been discussed at length here over the years. But I simply hate the current behaviour. It causes stress. It causes data issues. It causes embarrassment. It causes extra work. It’s entirely unnecessary. It’s terrible customer service  
All because someone at Affinity has a somewhat bizarre idea about how save dialogues should work that’s different from every other app. 
It’s just not good enough. Sort it out. I’m done with waiting patiently. 

I understand this is not fixed in v2. Very disappointing. 
 
I had been assuming faults like this weren’t being fixed in v1 because they would be in v2. 
 
The problem is that ‘save as’ dialog should start with the directory of the current open file. Not the location of the last saved file. Many reasons are given in the previous discussion which is now archived (link below).
 
The main overarching one is that this is the way that all other apps work. So it is like a trap. It is contrary to the way everyone expects things to work. If you work on multiple projects and you have a well structured project folder system, the chances are that one folder for one project looks much like the folder for any other project. To spot you’re saving a file in the wrong place is virtually impossible.
The usability is horrendous. 
 
https://forum.affinity.serif.com/index.php?/topic/17825-default-location-for-save-as-and-export/page/1/

Personally, I strongly think that the default behaviour for save as should be to save in the same location as the current file. 
 
If you’re working on a project, the vast majority of times you want to do a save as operation it would be in the same folder or a folder that’s close to in the folder tree hierarchy. 
 
That you might have been messing around with some random other file earlier in the day and that location would be the default save location makes no sense at all. 
 
However, I agree that having some kind of ability to override the default is reasonable. Just perhaps the overrides should be a bit less specific. 

I understand this is not fixed in v2. Very disappointing. 
 
I had been assuming faults like this weren’t being fixed in v1 because they would be in v2. 
 
The problem is that ‘save as’ dialog should start with the directory of the current open file. Not the location of the last saved file. Many reasons are given in the previous discussion which is now archived (link below).
 
The main overarching one is that this is the way that all other apps work. So it is like a trap. It is contrary to the way everyone expects things to work. If you work on multiple projects and you have a well structured project folder system, the chances are that one folder for one project looks much like the folder for any other project. To spot you’re saving a file in the wrong place is virtually impossible.
The usability is horrendous. 
 
https://forum.affinity.serif.com/index.php?/topic/17825-default-location-for-save-as-and-export/page/1/

Personally, I strongly think that the default behaviour for save as should be to save in the same location as the current file. 
 
If you’re working on a project, the vast majority of times you want to do a save as operation it would be in the same folder or a folder that’s close to in the folder tree hierarchy. 
 
That you might have been messing around with some random other file earlier in the day and that location would be the default save location makes no sense at all. 
 
However, I agree that having some kind of ability to override the default is reasonable. Just perhaps the overrides should be a bit less specific. 

I came here to check before buying v2. I honestly cannot believe they haven’t fixed this. Astonishing. 

Hi, thanks. I think it is reasonable to expect that a placed PDF looks like the file. I’d say this is essential.

I would also like this to be settable as a default option for paste.
I rarely want to paste with formatting. For now, I've altered the keyboard shortcut so that Command+V has a binding to Paste Without Format instead of Paste. I guess that's an OK solution for me, but I imagine lots of others will never do that.

I would also like this to be settable as a default option for paste.
I rarely want to paste with formatting. For now, I've altered the keyboard shortcut so that Command+V has a binding to Paste Without Format instead of Paste. I guess that's an OK solution for me, but I imagine lots of others will never do that.

I would also like this to be settable as a default option for paste.
I rarely want to paste with formatting. For now, I've altered the keyboard shortcut so that Command+V has a binding to Paste Without Format instead of Paste. I guess that's an OK solution for me, but I imagine lots of others will never do that.

Is there any plan to enable the flood select and flood fill tools to sample all visible layers? It is a major limitation currently that they only respect what is on the current active layer rather than what is visible.
It should be a tool option, both ways are valid and useful.

I would also like this to be settable as a default option for paste.
I rarely want to paste with formatting. For now, I've altered the keyboard shortcut so that Command+V has a binding to Paste Without Format instead of Paste. I guess that's an OK solution for me, but I imagine lots of others will never do that.

...to the mouse right-click pop-up menu. Thanks!

I hate to repeat myself, folks, but:
Hence:
… if you don't like it.
I've done that over a decade ago and never looked back.

I think a good behavior would be:
1.) Save As: Default to the current file's folder.
2.) Export (pdf etc, but also for palettes): Default to the folder where I last exported to, when the current document was open. At first time, use current folder as in 1.
(Also Corel has always been much smarter with that, for decades. To be fair, its a different price range. If the Mac Version of the Corel Suite would have came out 3 years earlier, I would now happily be using Corel.)
Affinity seems quite stubborn here. Looks like we have to buy DefaultFolderX to make the Affinity products complete.

Yeah this has been essentially broken for as long as I've been using Affinity apps. It is appallingly bad.
If you're just someone working on a hobby project at home, you probably wouldn't notice that the behaviour is so absolutely awful.
We work on multiple projects. Sometimes many in a single day. We are organised, so each project has a standard folder structure that we create when we start a new project. It means you can find files on projects you haven't worked on before or haven't worked on for a long time.
Trouble is, that the Affinity apps default to the last location used rather than the location of the current file as highlighted earlier in this thread.
Imagine that we have, for example, a Publisher folder for each project. When saving a new file, it can look for all intents and purposes like you're saving it in the right location because the folder is called 'Publisher'. But it isn't because it is defaulting to a save location of a Publisher folder in another project.
I cannot emphasise how seriously bad this is. So often we have to go searching around various folders to try to locate Affinity files that we thought we'd saved to the right locations but they ended up spuriously in the wrong place.
Please PLEASE fix this. It is another feature request that has been lingering for several years that really shouldn't be that difficult to fix. COME ON SERIF. Please.
@MEB

Yeah this has been essentially broken for as long as I've been using Affinity apps. It is appallingly bad.
If you're just someone working on a hobby project at home, you probably wouldn't notice that the behaviour is so absolutely awful.
We work on multiple projects. Sometimes many in a single day. We are organised, so each project has a standard folder structure that we create when we start a new project. It means you can find files on projects you haven't worked on before or haven't worked on for a long time.
Trouble is, that the Affinity apps default to the last location used rather than the location of the current file as highlighted earlier in this thread.
Imagine that we have, for example, a Publisher folder for each project. When saving a new file, it can look for all intents and purposes like you're saving it in the right location because the folder is called 'Publisher'. But it isn't because it is defaulting to a save location of a Publisher folder in another project.
I cannot emphasise how seriously bad this is. So often we have to go searching around various folders to try to locate Affinity files that we thought we'd saved to the right locations but they ended up spuriously in the wrong place.
Please PLEASE fix this. It is another feature request that has been lingering for several years that really shouldn't be that difficult to fix. COME ON SERIF. Please.
@MEB

I understand your sentiment of being realistic and providing advice, but part of the point of these forums is to communicate with Serif about problems and feature requests. 
The behaviour as it is currently is terrible. So it’s reasonable to hope that it might be fixed one day. Yes, I realise others might be OK with it as it is, but even after several years I still find it incredibly bad. 

I understand your sentiment of being realistic and providing advice, but part of the point of these forums is to communicate with Serif about problems and feature requests. 
The behaviour as it is currently is terrible. So it’s reasonable to hope that it might be fixed one day. Yes, I realise others might be OK with it as it is, but even after several years I still find it incredibly bad. 

Since the update to 1.8.6 under MacOS 10.15.7 the start performance of Affinity Photo is much slower that before with version 1.8.4.
 

...but the default should be "All Pages" as we all know.

Yes, it should.

We sort of have that already. From the File - Open dialog, look down the sidebar for Media - Photos and that will give you access to the images in your Apple Photos library. 

 
However, it's pretty clunky - sometimes it will initially only display my Photo Booth library. On top of that, if you open a file in this way, and then close it (even without editing),  the next time you run File - Open you start deep in the normally hidden Photos.library directory structure, and heaven knows what damage you could do to the database if you start messing with that.
I also don't know what the effect would be in Apple Photos if you opened an image in this way, edited and saved it.  Photos doesn't recognise .afphoto documents, so you'd have to manually flatten it to retain .jpg format. Even then I don't know what effect it would have on Apple Photos, and I'm somewhat reluctant to experiment with it. And I don't even want to begin to think about a workflow for raw files...