digikam default options
Locked
12
12
 
|
Hello, * Always show original images (deactivated by default)I thought it might be not a bad idea to let users activate/deactivate the following options during the initial setup wizard: * Update file timestamp when files are modified (activated by default) Please share your thoughts. Best regards, Andrey Goreev |
|
|
2017-01-12 16:49 GMT+01:00 Andrey Goreev <[hidden email]>:
This option is always turn on by default.
Done. We show original by default. I agree, we receive a lots of reports about items that disappear from icon-view because original files are hidden by default.
No. The handbook have been updated to describe all settings. The plan to include metadata settings panel in first run is not a good way. We have a warning at end of firstrun to explain that a lots of settings are available in setup panel and mostly all options are described in handbook now (or will be done). Gilles Caulier |
|
|
In reply to this post by AndriusWild
On jeudi 12 janvier 2017 08:49:06 CET Andrey Goreev wrote:
> Hello, > > I thought it might be not a bad idea to let users activate/deactivate the > following options during the initial setup wizard: > > * Update file timestamp when files are modified (activated by default) > * Always show original images (deactivated by default) > > I have a feeling that many users would prefer to have updating the file > timestamp box unchecked and show original images checked. Showing original images as default: yes; that avoids images appearing as 'not present' and considered 'lost' (see mailing list...) NOT updating timestamps as default: no, for at least one simple reason. If you mean the file "last-modified" timestamp, not updating that would break all "make-like" programs and scripts, that use that timestamp to see if a particular fiel needs treatment? If you mean the EXIF timestamps: when you stop updating EXIF DateTime, you break the expected dehaviour, with no benifit, as there is a DateTimeOriginal tag (which should remain unchanged). Basically, the program with default settings should have the least surprising behaviour. Not showing some images or not updating timestamps which reflect changes go against this principle. (Note: having those as switches that can be modified by the user is fine - we hope (s)he knows what (s)he is doing - but this is about the default settings). Remco P.S.: Exactly the same principle applies to (not) updating the thumbnail representing the undeveloped RAW file (discussed in a separate thread). |
|
|
2017-01-14 13:51 GMT+01:00 Remco Viëtor <[hidden email]>: On jeudi 12 janvier 2017 08:49:06 CET Andrey Goreev wrote: Ah i miss-understand your previous mail. The option is enabled by default and your want to see this option turned off now. Right ? Gilles Caulier |
|
|
On samedi 14 janvier 2017 13:55:04 CET Gilles Caulier wrote:
> 2017-01-14 13:51 GMT+01:00 Remco Viëtor <[hidden email]>: > > On jeudi 12 janvier 2017 08:49:06 CET Andrey Goreev wrote: > > > Hello, > > > > > > I thought it might be not a bad idea to let users activate/deactivate > > > the > > > following options during the initial setup wizard: > > > > > > * Update file timestamp when files are modified (activated by default) > > > * Always show original images (deactivated by default) > > > > > > I have a feeling that many users would prefer to have updating the file > > > timestamp box unchecked and show original images checked. > > > > Showing original images as default: yes; that avoids images appearing as > > 'not > > present' and considered 'lost' (see mailing list...) > > > > NOT updating timestamps as default: no, for at least one simple reason. > > If you mean the file "last-modified" timestamp, not updating that would > > break > > all "make-like" programs and scripts, that use that timestamp to see if a > > particular fiel needs treatment? > > Ah i miss-understand your previous mail. The option is enabled by default > and your want to see this option turned off now. Right ? > > Gilles Caulier It's my first mail in this thread, so, "which previous mail"? :^) My reply was to Andrey Goreev (the OP) For the record, I agree with what you stated as Digikam defaults in your earlier mail (Sat, 14 Jan 2017 11:10:12 +0000 (UTC)): Update file timestamps : YES Always show original images : YES |
|
|
Dear all,
This is exactly the second problem we have: when you modify the exif data of the JPG or RAW fle, for example for adding copyright information, or photograph title and description (important for some assignment and for some contests / prizes), the file timestamp is modified, which means the whole time order is screwed and when you then try to open the photographs with another editor or DAM tool. Would it be possible to have the option to switch off modification of the file timestamp when we only modify the exif data? Best Regards Corrado & Rina Quoting Remco Viëtor <[hidden email]>: > On samedi 14 janvier 2017 13:55:04 CET Gilles Caulier wrote: >> 2017-01-14 13:51 GMT+01:00 Remco Viëtor <[hidden email]>: >> > On jeudi 12 janvier 2017 08:49:06 CET Andrey Goreev wrote: >> > > Hello, >> > > >> > > I thought it might be not a bad idea to let users activate/deactivate >> > > the >> > > following options during the initial setup wizard: >> > > >> > > * Update file timestamp when files are modified (activated by default) >> > > * Always show original images (deactivated by default) >> > > >> > > I have a feeling that many users would prefer to have updating the file >> > > timestamp box unchecked and show original images checked. >> > >> > Showing original images as default: yes; that avoids images appearing as >> > 'not >> > present' and considered 'lost' (see mailing list...) >> > >> > NOT updating timestamps as default: no, for at least one simple reason. >> > If you mean the file "last-modified" timestamp, not updating that would >> > break >> > all "make-like" programs and scripts, that use that timestamp to see if a >> > particular fiel needs treatment? >> >> Ah i miss-understand your previous mail. The option is enabled by default >> and your want to see this option turned off now. Right ? >> >> Gilles Caulier > > It's my first mail in this thread, so, "which previous mail"? :^) > My reply was to Andrey Goreev (the OP) > > For the record, I agree with what you stated as Digikam defaults in your > earlier mail (Sat, 14 Jan 2017 11:10:12 +0000 (UTC)): > Update file timestamps : YES > Always show original images : YES |
|
|
In reply to this post by AndriusWild
I guess it is not clear what the "file timestamp" is and what is considered "file modifying". There are tons of date tags in metadata (try to "exiftool -s filename" one of your files has been modified few times using different programs. You will be surprised how many date/time tags are there. So which one being updated when the option is on? Also, is adding a keyword or caption or label or geolocation considered a file modifying? Or that only applies to an image that has been touched in Image Editor module? Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: cerp <[hidden email]> Date: 2017-01-14 6:50 AM (GMT-07:00) To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]> Subject: Re: digikam default options This is exactly the second problem we have: when you modify the exif data of the JPG or RAW fle, for example for adding copyright information, or photograph title and description (important for some assignment and for some contests / prizes), the file timestamp is modified, which means the whole time order is screwed and when you then try to open the photographs with another editor or DAM tool. Would it be possible to have the option to switch off modification of the file timestamp when we only modify the exif data? Best Regards Corrado & Rina Quoting Remco Viëtor <[hidden email]>: > On samedi 14 janvier 2017 13:55:04 CET Gilles Caulier wrote: >> 2017-01-14 13:51 GMT+01:00 Remco Viëtor <[hidden email]>: >> > On jeudi 12 janvier 2017 08:49:06 CET Andrey Goreev wrote: >> > > Hello, >> > > >> > > I thought it might be not a bad idea to let users activate/deactivate >> > > the >> > > following options during the initial setup wizard: >> > > >> > > * Update file timestamp when files are modified (activated by default) >> > > * Always show original images (deactivated by default) >> > > >> > > I have a feeling that many users would prefer to have updating the file >> > > timestamp box unchecked and show original images checked. >> > >> > Showing original images as default: yes; that avoids images appearing as >> > 'not >> > present' and considered 'lost' (see mailing list...) >> > >> > NOT updating timestamps as default: no, for at least one simple reason. >> > If you mean the file "last-modified" timestamp, not updating that would >> > break >> > all "make-like" programs and scripts, that use that timestamp to see if a >> > particular fiel needs treatment? >> >> Ah i miss-understand your previous mail. The option is enabled by default >> and your want to see this option turned off now. Right ? >> >> Gilles Caulier > > It's my first mail in this thread, so, "which previous mail"? :^) > My reply was to Andrey Goreev (the OP) > > For the record, I agree with what you stated as Digikam defaults in your > earlier mail (Sat, 14 Jan 2017 11:10:12 +0000 (UTC)): > Update file timestamps : YES > Always show original images : YES |
|
|
In reply to this post by cerp
Hi Corrado & Rina,
This option is available in configuration at Metadata -> Behavior -> Reading and Writing Metadata -> Update file timestamp when files are modified. Cheers, Simon On 14/01/17 14:50, cerp wrote: > Dear all, > > This is exactly the second problem we have: when you modify the exif > data of the JPG or RAW fle, for example for adding copyright > information, or photograph title and description (important for some > assignment and for some contests / prizes), the file timestamp is > modified, which means the whole time order is screwed and when you > then try to open the photographs with another editor or DAM tool. > Would it be possible to have the option to switch off modification of > the file timestamp when we only modify the exif data? > > Best Regards > > Corrado & Rina > > > > > > Quoting Remco Viëtor <[hidden email]>: > >> On samedi 14 janvier 2017 13:55:04 CET Gilles Caulier wrote: >>> 2017-01-14 13:51 GMT+01:00 Remco Viëtor <[hidden email]>: >>> > On jeudi 12 janvier 2017 08:49:06 CET Andrey Goreev wrote: >>> > > Hello, >>> > > >>> > > I thought it might be not a bad idea to let users >>> activate/deactivate >>> > > the >>> > > following options during the initial setup wizard: >>> > > >>> > > * Update file timestamp when files are modified (activated by >>> default) >>> > > * Always show original images (deactivated by default) >>> > > >>> > > I have a feeling that many users would prefer to have updating >>> the file >>> > > timestamp box unchecked and show original images checked. >>> > >>> > Showing original images as default: yes; that avoids images >>> appearing as >>> > 'not >>> > present' and considered 'lost' (see mailing list...) >>> > >>> > NOT updating timestamps as default: no, for at least one simple >>> reason. >>> > If you mean the file "last-modified" timestamp, not updating that >>> would >>> > break >>> > all "make-like" programs and scripts, that use that timestamp to >>> see if a >>> > particular fiel needs treatment? >>> >>> Ah i miss-understand your previous mail. The option is enabled by >>> default >>> and your want to see this option turned off now. Right ? >>> >>> Gilles Caulier >> >> It's my first mail in this thread, so, "which previous mail"? :^) >> My reply was to Andrey Goreev (the OP) >> >> For the record, I agree with what you stated as Digikam defaults in your >> earlier mail (Sat, 14 Jan 2017 11:10:12 +0000 (UTC)): >> Update file timestamps : YES >> Always show original images : YES > > > |
|
|
In reply to this post by AndriusWild
Wanted to add to my message below. I think adding any info to metadata should not be considered as "file modifying". Why would you add any metadata? To get your pictures organized, right? So why would mess with timestamps then? Original timestamps should be preserved. If you actually develop a picture that is a different case. Filestamp should be up to date. IMHO. Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Andrey Goreev <[hidden email]> Date: 2017-01-14 7:04 AM (GMT-07:00) To: [hidden email], digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]> Subject: Re: digikam default options I guess it is not clear what the "file timestamp" is and what is considered "file modifying". There are tons of date tags in metadata (try to "exiftool -s filename" one of your files has been modified few times using different programs. You will be surprised how many date/time tags are there. So which one being updated when the option is on? Also, is adding a keyword or caption or label or geolocation considered a file modifying? Or that only applies to an image that has been touched in Image Editor module? Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: cerp <[hidden email]> Date: 2017-01-14 6:50 AM (GMT-07:00) To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]> Subject: Re: digikam default options This is exactly the second problem we have: when you modify the exif data of the JPG or RAW fle, for example for adding copyright information, or photograph title and description (important for some assignment and for some contests / prizes), the file timestamp is modified, which means the whole time order is screwed and when you then try to open the photographs with another editor or DAM tool. Would it be possible to have the option to switch off modification of the file timestamp when we only modify the exif data? Best Regards Corrado & Rina Quoting Remco Viëtor <[hidden email]>: > On samedi 14 janvier 2017 13:55:04 CET Gilles Caulier wrote: >> 2017-01-14 13:51 GMT+01:00 Remco Viëtor <[hidden email]>: >> > On jeudi 12 janvier 2017 08:49:06 CET Andrey Goreev wrote: >> > > Hello, >> > > >> > > I thought it might be not a bad idea to let users activate/deactivate >> > > the >> > > following options during the initial setup wizard: >> > > >> > > * Update file timestamp when files are modified (activated by default) >> > > * Always show original images (deactivated by default) >> > > >> > > I have a feeling that many users would prefer to have updating the file >> > > timestamp box unchecked and show original images checked. >> > >> > Showing original images as default: yes; that avoids images appearing as >> > 'not >> > present' and considered 'lost' (see mailing list...) >> > >> > NOT updating timestamps as default: no, for at least one simple reason. >> > If you mean the file "last-modified" timestamp, not updating that would >> > break >> > all "make-like" programs and scripts, that use that timestamp to see if a >> > particular fiel needs treatment? >> >> Ah i miss-understand your previous mail. The option is enabled by default >> and your want to see this option turned off now. Right ? >> >> Gilles Caulier > > It's my first mail in this thread, so, "which previous mail"? :^) > My reply was to Andrey Goreev (the OP) > > For the record, I agree with what you stated as Digikam defaults in your > earlier mail (Sat, 14 Jan 2017 11:10:12 +0000 (UTC)): > Update file timestamps : YES > Always show original images : YES |
|
|
Well that is your philosophy. Mine is that anytime a file is
modified on disk (the metadata header is part of the file) the
timestamp should be updated. There is no correct philosophy, that is
why there is an option to set the behaviour to ones taste.
The usual (as in not photography related) behaviour is to change the timestamp on any file when it gets modified, so that is why this is the standard behaviour in digikam. On 14/01/17 15:14, Andrey Goreev wrote:
|
|
|
In reply to this post by AndriusWild
Well, I take pictures to capture moments. So why should the date of the moment be changed if I simply added an info in order to be able to find that picture later ? Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Simon Frei <[hidden email]> Date: 2017-01-14 7:24 AM (GMT-07:00) To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]> Subject: Re: digikam default options The usual (as in not photography related) behaviour is to change the timestamp on any file when it gets modified, so that is why this is the standard behaviour in digikam. On 14/01/17 15:14, Andrey Goreev wrote:
|
|
|
There is clearly a misconception here:
The "Date modified", "mtime" or whatever it is called property is NOT the time a picture was taken. That information is stored in the file itself, in the exif header. So the moment of your capture does not change at all unless you specifically do so using tools to modify the exif header of the file. On 14/01/17 15:30, Andrey Goreev wrote:
|
|
|
When digikam says "Update file timestamp when files are modified", does
it refer to the OS timestamp, or the file's internal (EXIF, XMP etc) metadata? I assume it means the OS timestamp. If so, this is a bit confusing since this option comes under the heading "Reading and Writing Metadata" and "Metadata" usually means EXIF, XMP etc that is written into the file itself. The Operating System's timestamp for that file is not "Metadata" in the sense that the word "Metadata" is used everywhere else in digikam. On Sat, 2017-01-14 at 15:43 +0100, Simon Frei wrote: > There is clearly a misconception here: > The "Date modified", "mtime" or whatever it is called property is NOT > the time a picture was taken. That information is stored in the file > itself, in the exif header. So the moment of your capture does not > change at all unless you specifically do so using tools to modify the > exif header of the file. > > On 14/01/17 15:30, Andrey Goreev wrote: > > Well, I take pictures to capture moments. So why should the date of > > the moment be changed if I simply added an info in order to be able > > to find that picture later ? > > > > > > > > Sent from my Samsung Galaxy smartphone. > > > > -------- Original message -------- > > From: Simon Frei <[hidden email]> > > Date: 2017-01-14 7:24 AM (GMT-07:00) > > To: digiKam - Home Manage your photographs as a professional with > > the power of open source <[hidden email]> > > Subject: Re: digikam default options > > > > Well that is your philosophy. Mine is that anytime a file is > > modified on disk (the metadata header is part of the file) the > > timestamp should be updated. There is no correct philosophy, that > > is why there is an option to set the behaviour to ones taste. > > The usual (as in not photography related) behaviour is to change > > the timestamp on any file when it gets modified, so that is why > > this is the standard behaviour in digikam. > > > > On 14/01/17 15:14, Andrey Goreev wrote: > > > Wanted to add to my message below. > > > I think adding any info to metadata should not be considered as > > > "file modifying". Why would you add any metadata? To get your > > > pictures organized, right? So why would mess with timestamps > > > then? Original timestamps should be preserved. > > > If you actually develop a picture that is a different case. > > > Filestamp should be up to date. > > > IMHO. > > > > > > Sent from my Samsung Galaxy smartphone. > > > > > > -------- Original message -------- > > > From: Andrey Goreev <[hidden email]> > > > Date: 2017-01-14 7:04 AM (GMT-07:00) > > > To: [hidden email], digiKam - Home Manage your photographs as a > > > professional with the power of open source <[hidden email] > > > > > > > Subject: Re: digikam default options > > > > > > I guess it is not clear what the "file timestamp" is and what is > > > considered "file modifying". > > > > > > There are tons of date tags in metadata (try to "exiftool -s > > > filename" one of your files has been modified few times using > > > different programs. You will be surprised how many date/time tags > > > are there. So which one being updated when the option is on? > > > > > > Also, is adding a keyword or caption or label or geolocation > > > considered a file modifying? Or that only applies to an image > > > that has been touched in Image Editor module? > > > > > > > > > Sent from my Samsung Galaxy smartphone. > > > > > > -------- Original message -------- > > > From: cerp <[hidden email]> > > > Date: 2017-01-14 6:50 AM (GMT-07:00) > > > To: digiKam - Home Manage your photographs as a professional with > > > the power of open source <[hidden email]> > > > Subject: Re: digikam default options > > > > > > Dear all, > > > > > > This is exactly the second problem we have: when you modify the > > > exif > > > data of the JPG or RAW fle, for example for adding copyright > > > information, or photograph title and description (important for > > > some > > > assignment and for some contests / prizes), the file timestamp > > > is > > > modified, which means the whole time order is screwed and when > > > you > > > then try to open the photographs with another editor or DAM > > > tool. > > > Would it be possible to have the option to switch off > > > modification of > > > the file timestamp when we only modify the exif data? > > > > > > Best Regards > > > > > > Corrado & Rina > > > > > > > > > > > > > > > > > > Quoting Remco Viëtor <[hidden email]>: > > > > > > > On samedi 14 janvier 2017 13:55:04 CET Gilles Caulier wrote: > > > >> 2017-01-14 13:51 GMT+01:00 Remco Viëtor <remco.vietor@wanadoo. > > > fr>: > > > >> > On jeudi 12 janvier 2017 08:49:06 CET Andrey Goreev wrote: > > > >> > > Hello, > > > >> > > > > > >> > > I thought it might be not a bad idea to let users > > > activate/deactivate > > > >> > > the > > > >> > > following options during the initial setup wizard: > > > >> > > > > > >> > > * Update file timestamp when files are modified (activated > > > by default) > > > >> > > * Always show original images (deactivated by default) > > > >> > > > > > >> > > I have a feeling that many users would prefer to have > > > updating the file > > > >> > > timestamp box unchecked and show original images checked. > > > >> > > > > >> > Showing original images as default: yes; that avoids images > > > appearing as > > > >> > 'not > > > >> > present' and considered 'lost' (see mailing list...) > > > >> > > > > >> > NOT updating timestamps as default: no, for at least one > > > simple reason. > > > >> > If you mean the file "last-modified" timestamp, not updating > > > that would > > > >> > break > > > >> > all "make-like" programs and scripts, that use that > > > timestamp to see if a > > > >> > particular fiel needs treatment? > > > >> > > > >> Ah i miss-understand your previous mail. The option is enabled > > > by default > > > >> and your want to see this option turned off now. Right ? > > > >> > > > >> Gilles Caulier > > > > > > > > It's my first mail in this thread, so, "which previous mail"? > > > :^) > > > > My reply was to Andrey Goreev (the OP) > > > > > > > > For the record, I agree with what you stated as Digikam > > > defaults in your > > > > earlier mail (Sat, 14 Jan 2017 11:10:12 +0000 (UTC)): > > > > Update file timestamps : YES > > > > Always show original images : YES > > > > > > > > > > > > |
|
|
In reply to this post by AndriusWild
On samedi 14 janvier 2017 07:30:08 CET Andrey Goreev wrote:
> Well, I take pictures to capture moments. So why should the date of the > moment be changed if I simply added an info in order to be able to find > that picture later ? There is a tag reflecting the time the image was taken. That one is not (and should not be) modified on any update, afaik. Also, we were talking about the best default for a configuration option. If you do not like the default, you can change it. But for me, a timestamp that's supposed to record the date/time an image was changed should _as_a_default_ do exactly that, to avoid surprising (new) users. Remco. |
|
|
In reply to this post by AndriusWild
On samedi 14 janvier 2017 16:01:34 CET cerp wrote:
> Dear Simon, > > In our case it is unflagged, but digikam still changes the timestamp > of the file (in the filesystem on the disk) .... which means when you > open with a filemanager or a different DAM tool the picture order is > completely screwed. I'm not sure Digikam has anything to say in that decision. File saving is handed off to a driver in the system (rather evident, once you realise how many file systems exists: Linux has at least 5 that it can handle: BTFRS, Ext4, NFS, Fat, NTFS; there are probably more that I've never seen/ used. Afaik, it's the driver that as a matter of course adjusts the time stamps in the file system. |
|
|
It is digikam that changes the timestamp, not the filesystem. I do not
understand your point. Best, Quoting Remco Viëtor <[hidden email]>: > On samedi 14 janvier 2017 16:01:34 CET cerp wrote: >> Dear Simon, >> >> In our case it is unflagged, but digikam still changes the timestamp >> of the file (in the filesystem on the disk) .... which means when you >> open with a filemanager or a different DAM tool the picture order is >> completely screwed. > > I'm not sure Digikam has anything to say in that decision. > File saving is handed off to a driver in the system (rather evident, once you > realise how many file systems exists: Linux has at least 5 that it > can handle: > BTFRS, Ext4, NFS, Fat, NTFS; there are probably more that I've never seen/ > used. Afaik, it's the driver that as a matter of course adjusts the time > stamps in the file system. |
|
|
In reply to this post by AndriusWild
I don't agree. Any options that can "harm" an inattentive user. Any date changes are a harm. For example, I installed digikam and imported my pictures. Some of them went to Miscellaneous / Places / zoo instead of Places / zoo. For sure I changed it right away but I was not aware of that timestamp update option being turned on and changed the date of 300+ files. For sure it might be considered as a user issue but again, I think user should be protected. Let's at least allow users to turn that option on/off in the initial setup wizard. Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Remco Viëtor <[hidden email]> Date: 2017-01-14 8:11 AM (GMT-07:00) To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]> Subject: Re: digikam default options > Well, I take pictures to capture moments. So why should the date of the > moment be changed if I simply added an info in order to be able to find > that picture later ? There is a tag reflecting the time the image was taken. That one is not (and should not be) modified on any update, afaik. Also, we were talking about the best default for a configuration option. If you do not like the default, you can change it. But for me, a timestamp that's supposed to record the date/time an image was changed should _as_a_default_ do exactly that, to avoid surprising (new) users. Remco. |
|
|
In reply to this post by AndriusWild
Cerp I think Linux does not save "date created" for files on only keeps "date modified" instead. So if you are using Linux and updated file stamps you lost chronological order in the file browser (nautilus, etc.) Windows keeps both "date created" and "date modified" as well as its file explorer allows users to sort files by any date including exif date taken. So if you are a Linux user you get harmed by digikam for not going through all the options in the beginning. You can fix the dates using exiftool (exiv2 will probably do that too) but that's at least 30 min of your life you will never get back. Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: cerp <[hidden email]> Date: 2017-01-14 8:25 AM (GMT-07:00) To: Remco Viëtor <[hidden email]> Cc: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]> Subject: Re: digikam default options understand your point. Best, Quoting Remco Viëtor <[hidden email]>: > On samedi 14 janvier 2017 16:01:34 CET cerp wrote: >> Dear Simon, >> >> In our case it is unflagged, but digikam still changes the timestamp >> of the file (in the filesystem on the disk) .... which means when you >> open with a filemanager or a different DAM tool the picture order is >> completely screwed. > > I'm not sure Digikam has anything to say in that decision. > File saving is handed off to a driver in the system (rather evident, once you > realise how many file systems exists: Linux has at least 5 that it > can handle: > BTFRS, Ext4, NFS, Fat, NTFS; there are probably more that I've never seen/ > used. Afaik, it's the driver that as a matter of course adjusts the time > stamps in the file system. |
|
|
In reply to this post by AndriusWild
I can only repeat myself:
There is clearly a misconception here:
The "Date modified", "mtime" or whatever it is called property is
NOT the time a picture was taken. That information is stored in the
file itself, in the exif header. So the moment of your capture does
not change at all unless you specifically do so using tools to
modify the exif header of the file.
There is no harm in updating the modified time/mtime. This is not
part of the file, it is a property of the file in the filesystem. It
has NOTHING AT ALL to do with time you captured your image. It is
used for stuff like backuping, syncing, ...So please change the option if you must (it is not a good idea as you don't seem to understand it), but the standard behaviour is correct. On 14/01/17 16:38, Andrey Goreev wrote:
|
|
|
In reply to this post by AndriusWild
On Sat, Jan 14, 2017 at 07:14:54AM -0700, Andrey Goreev wrote:
> Wanted to add to my message below. > > I think adding any info to metadata should not be considered as "file > modifying". Why would you add any metadata? To get your pictures > organized, right? So why would mess with timestamps then? Original > timestamps should be preserved. > The *files* timestamp (there are three actually) is operating system information and is an indicator to the operating system and is used by other programs and the OS to manage the file. If I modify a file by changing the metadata I *do* want to change the timestamp because this tells the operatiny system (and other software) that the file has been modified and should, for example, be backed up. Quite a lot of backup programs in particular rely on the file timestamps to decide whether a file should be backed up. The times in the metadata are for use by such as Digikam. -- Chris Green |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |