[digikam] [Bug 370491] New: Checkboxes in Metadata Views Setup Don't Reflect Current Selection

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 370491] New: Checkboxes in Metadata Views Setup Don't Reflect Current Selection

bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=370491

            Bug ID: 370491
           Summary: Checkboxes in Metadata Views Setup Don't Reflect
                    Current Selection
           Product: digikam
           Version: 5.2.0
          Platform: MS Windows
                OS: MS Windows
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: setup
          Assignee: [hidden email]
          Reporter: [hidden email]

In Configure > Metadata > Views, there are no checkboxes selected for currently
enabled fields. For example, in EXIF metadata view, "GPS Altitude Reference" is
shown by default. However "GPSAltitudeRef" does not have a check against it in
the EXIF metadata view configuration.

A secondary problem is that if "GPSAltitudeRef" is selected for view, all
currently displayed metadata items except "GPSAltitudeRef" are then switched
off in the metadata view.

Reproducible: Always

Steps to Reproduce:
1. In EXIF Metadata view setup, select GPSDestinationDistance.
2. Go to metadata view. All items except GPSDestinationDistance are removed
from the view.
3.

Actual Results:  
See pictures.

Expected Results:  
Check marks should be shown against default view items in the setup.

--
You are receiving this mail because:
You are the assignee for the bug.
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 370491] Checkboxes in Metadata Views Setup Don't Reflect Current Selection

bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=370491

--- Comment #1 from [hidden email] ---
Created attachment 101528
  --> https://bugs.kde.org/attachment.cgi?id=101528&action=edit
Image showing problem.

--
You are receiving this mail because:
You are the assignee for the bug.
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 370491] Checkboxes in Metadata Views Setup Don't Reflect Default Selection

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=370491

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Checkboxes in Metadata      |Checkboxes in Metadata
                   |Views Setup Don't Reflect   |Views Setup Don't Reflect
                   |Current Selection           |Default Selection

--
You are receiving this mail because:
You are the assignee for the bug.
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 370491] Checkboxes in Metadata Views Setup Don't Reflect Default Selection

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=370491

Maik Qualmann <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #2 from Maik Qualmann <[hidden email]> ---
The behavior is normal for the custom filter. It is actually a filter. If no
entry is selected, the filter is off. Otherwise, you must select all that you
want to display.

Maik

--
You are receiving this mail because:
You are the assignee for the bug.
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 370491] Checkboxes in Metadata Views Setup Don't Reflect Default Selection

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=370491

--- Comment #3 from [hidden email] ---
Ok thanks Maik.

I'm just wondering about the case  where the user is happy with the default
list and they just want to add one more item. It then seems a lot of effort to
re-apply the items that were previously already displayed, assuming you can
remember the list.

Is there no case for initialising the custom filter to the same as the current
defaults?

Thanks.

--
You are receiving this mail because:
You are the assignee for the bug.