https://bugs.kde.org/show_bug.cgi?id=405860
--- Comment #15 from caulier.gil...@gmail.com ---
Maik,
This is another Exif value to populate in database. Remember the time zone wish
too reported in another bugzilla entry.
Gilles
--
You are receiving this mail because:
You are watching all bug ch
https://bugs.kde.org/show_bug.cgi?id=405860
caulier.gil...@gmail.com changed:
What|Removed |Added
Severity|normal |wishlist
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=405860
--- Comment #14 from Christian Gruber ---
Further observation: It seems to be necessary to have a field in the list that
is not available.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405860
--- Comment #13 from Christian Gruber ---
I have experimented a bit, and when I have a certain number of entries (5 or
so, I do not know exactly), the effect appears. A few more, and the effect
vanishes again.
--
You are receiving this mail because:
Y
https://bugs.kde.org/show_bug.cgi?id=405860
--- Comment #12 from Maik Qualmann ---
Works here without problems. For example, there are the entries double for
image information or photo information. Therefore, you have the "unavailable"
display when you select the example of the focal length of im
https://bugs.kde.org/show_bug.cgi?id=405860
--- Comment #11 from Christian Gruber ---
I added a few EXIF entries that are displayed, and suddenly 10 entries more
than I selected are displayed. I have the tab on "EXIF", and when I click on
the triangle left of the Search field, the "user defined"
https://bugs.kde.org/show_bug.cgi?id=405860
--- Comment #10 from Christian Gruber ---
How can be the name of the used EXIF fields be determined? I do not know what I
did exactly, but all the displayed EXIF information vanished. I then decided to
put the interesting fields back one after the other
https://bugs.kde.org/show_bug.cgi?id=405860
--- Comment #9 from Christian Gruber ---
When it is not planned to keep the same database scheme like it was in the
design phase and let it evolve, I think that a good time to do this is a change
in the major version number (for example 5 to 6). I do no
https://bugs.kde.org/show_bug.cgi?id=405860
--- Comment #8 from Maik Qualmann ---
That too would be possible, but it would be a major change. Alternatively, you
can see the exposure correction from the selected image in the right metadata
side bar. It is also possible to use a filter that only di
https://bugs.kde.org/show_bug.cgi?id=405860
--- Comment #7 from Christian Gruber ---
I did not mean to store all the EXIF data in a BLOB without structure, but to
make a table "exif" or something like that, with key and value as columns and a
foreign key to the picture file. This way it would be
https://bugs.kde.org/show_bug.cgi?id=405860
--- Comment #6 from Maik Qualmann ---
It's not about somehow saving the EXIF metadata in a BLOB field. It must also
be possible to associate this data with SQL queries by e.g. to include all
images with a focal length of > 100mm and an exposure compensa
https://bugs.kde.org/show_bug.cgi?id=405860
--- Comment #5 from Christian Gruber ---
It would be much more flexible and easier for the developer if the EXIF
information was stored as key-value-pair and not as a dedicated row in the
database
--
You are receiving this mail because:
You are watchi
https://bugs.kde.org/show_bug.cgi?id=405860
--- Comment #4 from caulier.gil...@gmail.com ---
Extracting this information from file is very easy with digiKam core
implementation. This is not the problem.
All elementary information shown in file properties view are stored also in the
database. Why
https://bugs.kde.org/show_bug.cgi?id=405860
--- Comment #3 from Christian Gruber ---
Why is it hard coded anyway?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405860
--- Comment #2 from Christian Gruber ---
This information is stored in the EXIF information of the picture, and can be
displayed e.g. in gwenview. I think this is a very useful information that can
be very handy.
In Panasonic DMC-FZ1000 it is stored in
https://bugs.kde.org/show_bug.cgi?id=405860
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #1 from Maik
https://bugs.kde.org/show_bug.cgi?id=405860
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
Com
17 matches
Mail list logo
