Hi Andy,
perhaps it is not in version 4.0.3a3 that I daily use, but would it be possible to add an extra step in the add files... feature: if a file of the same name is present, instead of deleting and recreating it, propose to keep the file and replace the data fork or the resource fork (if present).

I code in Merlin32, and add S16 assembled file with Ciderpress. Problem: my S16 has a resource fork that I must recreate each time.

Thank you,
Antoine

On Thursday, July 15, 2021 at 10:49:39 AM UTC-7, ntn.v...@gmail.com wrote:
> perhaps it is not in version 4.0.3a3 that I daily use, but would it be possible to add an extra step in the add files... feature: if a file of the same name is present, instead of deleting and recreating it, propose to keep the file and replace the data fork or the resource fork (if present).
>
> I code in Merlin32, and add S16 assembled file with Ciderpress. Problem: my S16 has a resource fork that I must recreate each time.

Doing this generally would be a bad idea, since it could result in things being merged when they should be replaced, and other weird situations. Making it an option is a little complicated, because the code for different destinations (disk image, ShrinkIt archive, etc.) handles forked files independently. The code for disk images currently gathers up the complete set of files being added, merges forked files into a single entity, and then does the "replace existing" stuff if it finds something with the same name.

The easiest way to work with the current implementation is to keep a copy of the resource fork next to the S16 on the Windows filesystem (with appropriate filename extension), and just add them both at the same time. This could be a bit annoying if the resource fork is also changing regularly.