SC Setting: "Save Overwrite" and "Copy Tags"

[Filehero]

Hi Don,

can SC setting(p) be extended to support

Code: Select all

SaveOverwrite: 0 | no Save Overwrite is applied during Custom Copy operations
                   (requires CustomCopy to be activated)
               1 | Save Overwrite is applied during Custom Copy operations
                   (requires CustomCopy to be activated)
               r | Restore previous setting


CopyTags:      0 | Tags (labels, tags, comments) are not copied on copy/backup operations
               1 | Tags (labels, tags, comments) are copied on copy/backup operations
               r | Restore previous setting

Thanks,
Filehero

[Filehero]

Hi Don,

any chance for being considered?

Thanks,
FH

[admin]

Yup.

[admin]

Uhm, spoke too soon. This would be 4 settings:

TagCopyTagsOnCopy
TagCopyTagsOnBackup
SafeOverwrite
BackupSafeOverwrite

And there are many more like these. I think I have to draw a line somewhere.

[Filehero]

I think I have to draw a line somewhere.

I see.

The wish for a "SafeOverwrite" handle result from a strange observation made with Custom Copy, described here.

Maybe it could be addressed differently?

[admin]

OK, I guess the addition of SafeOverwrite can be justified.

[Filehero]

Code: Select all

v18.10.0001 - 2017-07-13 18:43
    + Scripting commands setting/settingp enhanced: New named argument 
      "safeoverwrite" to temporarily enable/disable Custom Copy "Safe Overwrite".

Thanks.

[Filehero]

With 18.10.0002 and a code like

Code: Select all

  setting("UseCustomCopy", 1);
  setting("SafeOverwrite", 0);
  copyto(gpc($targetFile), $sourceFile, , , -1);

I still get this tab renaming in the editor.

Code: Select all

  settingp("SafeOverwrite", 0);

also has no effects when checked against the configuration.

?

[admin]

Frankly I did not even test it. I come back later...

[admin]

Should be fixed in next beta.

[Filehero]

Should be fixed in next beta.

Fix confirmed. What a relief, thanks.