Jump to content

Recommended Posts

Posted

Even at Version 1.10 it´s still possible to delete open files (= files you are currently working on) because the files are not locked.
Think about teams working with data on common shares on file-servers...

Posted
20 minutes ago, Fritz_H said:

As it seems, someone moved my posting here

Had to be one of the Moderators or Staff.

 

20 minutes ago, Fritz_H said:

I am sure, that this is simply a bug

I think they consider this not a bug, because the image you have opened in AP, is now a afphoto file, not the original. So it can be manipulated and then saved, or exported. This creates a new (copy) of the original, unless you choose export to another format.

I think this is better, than having to deal with the file being deleted while being worked on, which might lead to corruption or loss of improvements. Someone else deletes the file, no big deal, just save it.

Affinity Photo 2.5..; Affinity Designer 2.5..; Affinity Publisher 2.5..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD

Posted
19 hours ago, Ron P. said:

I think they consider this not a bug, because the image you have opened in AP, is now a afphoto file, not the original. So it can be manipulated and then saved, or exported. This creates a new (copy) of the original, unless you choose export to another format.

Not sure it's about this.

The problem can be tested without a server and different people working on the same file:

  • Open a file (i.e. Test.afphoto) in AP and modify it,
  • you can also open the same file in AD an modify it without warning
  • and also in APub and modify it without warning...

You can alternate modifying the file with one of the app and check the display in Explorer, it'll look like the last saved done in the last app used.

 

When working alone, you usually avoid this, but when working with other people on servers, you want to be warned that a file is already in use and somebody's work won't erase somebody else work... Especially when sometimes you can only open a file just to check some proprieties or layers, modify visibily to check something else, and hours later, when thinking of closing the file, if it asks you to save it because it was modified (and since the history will have been modified), not remembering if you did something important, you'll save it. Probably erasing other people work.

Strangely, I was able to save few times in each app, until at some point AP noticed the file was different. From this point, the other apps provided the same warning.

2021-08-08_073406.png.d5653487e6b0ad41a1ca916ba40c7247.png

 

So, next test:

  • I close the file in one of the apps with the warning,
  • and re-open it.
  • I modify the file,
  • I save it without problem, not knowing it's already in use by another app, without warning in this app.

 

If the usual lock system with a warning about the file being already used by someone else/some other app existed, it wouldn't happen.

As it is, it's not a problem when everyone work on servers on an open space, you just need to ask: "Who's using this file? I need to modify it also...", but with people working at different places, you begin dupplicating files, and sometimes for no reasons and it begins to be a problem, since the last one saved isn't always the one with the meaningfull modifications (i.e. only history modifications).

Posted
On 8/7/2021 at 11:30 AM, Fritz_H said:

although I am sure, that this is simply a bug.

Is it declared somewhere, that the file will be locked after opening? If so, then it is really a bug, that file is not locked. If it is not declared, then the current behavior of the application is definitely not a bug - it's just a proposal that does not suit you, and therefore it is appropriate to submit a proposal to modify the functionality, which Serif evaluates, and maybe sometimes implements.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.7.2948 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Posted
53 minutes ago, LondonSquirrel said:

File locking is not the job of an app like the Affinity range. File locking is handled at the OS level.

It is not true. File locking is job for OS, but on application request.
https://docs.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-lockfile

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.7.2948 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Posted
6 minutes ago, LondonSquirrel said:

Did you read my post? Evidently not: 'Windows locks are handled differently.'

Yes, I read - and you're obviously wrong.

1 hour ago, LondonSquirrel said:

File locking is not the job of an app like the Affinity range.

 

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.7.2948 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | 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.