Skip to content

Basing file path in checksum file based on save location is weird. #86

Description

@alphaniner

If I open a directory (eg. test), select some files, run Create Checksum File... and save the checksum file in place, the file paths in the checksum file are as expected:

ab108e300a1483b7fd018bdd15bc6e8df8d0ea01a57bf08508bb77f92a8a1f1a *foo\foobar.txt
0c105a96919a411c86426e54a570bbdb57e6deb312ed0a90e2c91baa3d68e91b *bar.txt

If I save the checksum file in the parent directory, test\ is prepended to all file paths:

ab108e300a1483b7fd018bdd15bc6e8df8d0ea01a57bf08508bb77f92a8a1f1a *test\foo\foobar.txt
0c105a96919a411c86426e54a570bbdb57e6deb312ed0a90e2c91baa3d68e91b *test\bar.txt

If saved to a different drive, the checksum file contains the full paths.

This is unexpected and IMO undesired. If this is intended behaviour please consider making it possible to disable it. Thanks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions