* Ralf M. <[email protected]> [04-10-21 22:26]:
> Thanks for testing.
> Today I had some time to figure out why it works for you but not for me.
>
> "darktable -d all" didn't tell me anything (no debug messages at all).
>
> Trying out all sorts of combinations I finally found:
>
>   Move doesn't move on Windows if
>   a) the destination directory is on a different drive
>    AND
>   b) the image file has the readonly attribute set.
>
> dt moves non-ro-images from one drive to another, and moves ro-images within
> one drive, but the combination doesn't work: The image file is copied to the
> destination, but the original and the sidecar file stay in the source
> directory.
>
> It's strange as the Windows Explorer happily moves ro-files from one drive
> to another without even asking for confirmation.
>
> I got what I wanted by temporarily removing the readonly attribute.
>
> Maybe this information is helpful to others.
>
> Best regards,
> Ralf M.
>
> Am 06.04.2021 um 00:31 schrieb Terry Pinfold:
> > I am using Windows build 3.4.1.1 and the function of move worked fine
> > for me when I just tested it.
> >
> > On Tue, 6 Apr 2021 at 06:33, Guillermo Rozas <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> >         Am I doing anything wrong?
> >         What is the correct procedure to achieve what I expected move to do?
> >
> >
> >         I'm using dt 3.4.1.1 on Windows.
> >         The images to be moved are TIFFs (film scans).
> >         Source and destination directory are on different volumes, i.e.
> >         the move
> >         means in reality copy and delete source.
> >
> >
> >     You're doing it right, and I just tested it on Linux and it works
> >     correctly.  Maybe a Windows-related bug, but I can't confirm it as I
> >     don't have a darktable installation on Windows.
> >
> >     Best regards,
> >     Guillermo
> >
> >     
> >____________________________________________________________________________
> >     darktable user mailing list to unsubscribe send a mail to
> >     [email protected]
> >     <mailto:darktable-user%[email protected]>
> >


and the action is quite expected
read-only files may be copied but not removed or executed.
that is the reason for "read-only"

why are you giving read-only permissions to the files?




-- 
(paka)Patrick Shanahan       Plainfield, Indiana, USA          @ptilopteri 
http://en.opensuse.org    openSUSE Community Member    facebook/ptilopteri 
http://wahoo.no-ip.org        Photo Album: http://wahoo.no-ip.org/gallery2 
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]

Reply via email to