[digikam] [Bug 479092] New: Increase the number of recent tags

2023-12-27 Thread Peter Albrecht
https://bugs.kde.org/show_bug.cgi?id=479092

Bug ID: 479092
   Summary: Increase the number of recent tags
Classification: Applications
   Product: digikam
   Version: 8.2.0
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Tags-Engine
  Assignee: digikam-bugs-n...@kde.org
  Reporter: p...@crazymonkeys.de
  Target Milestone: ---

SUMMARY
Please increase the number of recent tags, which digikam does remember.


STEPS TO REPRODUCE
1. create 12 tags with the names "personA", "personB", ... "personK", "personL"
2. select "image001.jpg", in view "Captions > Tags" assign the tags: "personA",
"personB", "personC", "personD", "personE", "personF"
3. click the "Apply" button to save the tag assignment
4. select "image002.jpg", in view "Captions > Tags" assign the tags: "personG",
"personH", "personI", "personJ", "personK", "personL"
5. click the "Apply" button to save the tag assignment
6. select "image003.jpg", in view "Captions > Tags" set focus in the input box
"Enter tag here"
7. start typing "person"

OBSERVED RESULT
You can see a list of tags matching the entered tag String "person". The most
recent 10 tags ("personL" to "personC") are printed in bold font and can be
found at the top of the list. The most recent tag "personL" is the top entry in
this list.
This is very helpful, since chances are very high, that the persons on the last
picture can also be seen on the current picture. And if this person is listed
near the top of this tag list, I can pick it with very little effort (= key
presses).

WHERE IS THE PROBLEM?
My "problem": When I take pictures of family events, there might be about 30
persons on these events. And the people on e.g. picture 3 might appear on
picture 16 again. But pictures 4 to 15 show 12 different people, so the persons
of picture 3 are no longer in the "recent tags" list. When tagging pictures 16,
I have to search* them in the "all tags" list, which contains 280 entries at
the moment.

*) Of course, I won't search the "all tags" list for those entries. I just keep
typing more letters of their tagname, until the list of matching tags is small
enough. But more typing per tag means more time per tag. And if you assign 500
tags for one big event, this time might add up.

MY WISH
Please increase the number of "recent tags" digikam does remember. 30 might be
a good value (for me). Others might need 50. But you can also think about
setting this to infinite and remember all tags in the order of their last use.
Is there anything against the latter solution?

As far as I understand, the relevant line of code is in
"core/libs/database/coredb/coredb.cpp", method "void
CoreDB::addItemTag(qlonglong imageID, int tagID, bool newTag)", line 3164:

if (d->recentlyAssignedTags.size() > 10)

ADDITIONAL INFORMATION
If you rightclick a picture, the context menu shows "Assign Tag". Selecting
this menu item opens a submenu which shows the 10 recently used tags. This list
should still show only the top 10 recently used tags, because 30 / 50 /
infinite tags are not good for this ui format.

SOFTWARE/OS VERSIONS
Digikam App Image 8.2.0
Linux/KDE Plasma: Debian 12
KDE Plasma Version: ?
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11

Thank you for your very good work on digikam!

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 463343] Ability to create customized group of tags.

2023-12-27 Thread Peter Albrecht
https://bugs.kde.org/show_bug.cgi?id=463343

--- Comment #6 from Peter Albrecht  ---
I have another issue, which might be "fixed" with the proposed "tag groups": I
use tags for people and I am have been tagging photos with digikam for a long
time by now. In the meantime some of those persons have died (or moved away).
So I won't need these tags while tagging new photos. But, of course, I want to
keep these tags on the old photos.
Having the ability to focus on tags with "people alive", while tagging new
photos, will speed up this process.

One thought about the implementation: I think, it would be handy, to have the
ability to assign one tag (e.g. "John Doe") to more than one group (e.g.
"People living in Springfield", "People alive", "My bowling group", ...). So I
can pick the best fitting group of tags, when tagging the 200 pictures of our
"bowling group event last Saturday".

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 463343] Ability to create customized group of tags.

2023-12-27 Thread Peter Albrecht
https://bugs.kde.org/show_bug.cgi?id=463343

Peter Albrecht  changed:

   What|Removed |Added

 CC||p...@crazymonkeys.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio-extras] [Bug 412257] kiod5 doesn't release usb device when it is not in use

2022-01-21 Thread Peter Albrecht
https://bugs.kde.org/show_bug.cgi?id=412257

--- Comment #17 from Peter Albrecht  ---
Additionally to the "release" action (see previous comment), I would be glad to
have a "disable" option, too. 

I do not use KIO MTP at all. But I use MTP with other applications a lot, so it
would be cumbersome to always click the "release" action before I can use MTP
in other applications. Maybe the option "disable kio mtp" can be put in KDE
settings dialog.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio-extras] [Bug 412257] kiod5 doesn't release usb device when it is not in use

2021-12-18 Thread Peter Albrecht
https://bugs.kde.org/show_bug.cgi?id=412257

Peter Albrecht  changed:

   What|Removed |Added

 CC||p...@crazymonkeys.de

--- Comment #5 from Peter Albrecht  ---
Another workaround, I have found:
If you do not use KIO MTP at all (since you only use something like "jmtpfs"),
you can "disable kmtpd":

# chmod 000 /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kiod/kmtpd.so

After restarting, mounting my android mobile phone with jmtpfs (MTP protocol)
worked again.

Thanks to user "arkonbob" at reddit for bringing up this solution:
https://www.reddit.com/r/kde/comments/mvrtck/restarting_kiod/

I am using Debian 11 (Bullseye):
* KDE Frameworks 5.78.0
* Qt 5.15.2

-

Another workaround is to switch to a runlevel without graphical desktop. This
stops KDE and KIOD. (In my case I want to run some scripts to backup the data
on my mobile phone, so I don't need a graphical desktop while these scripts are
running.)
I you use systemd, you can do the following:
* log out from KDE session
* go to console (e.g. CTRL + ALT + F2)
* log in at the console as root
* switch the runlevel:  # systemctl isolate multi-user.target
* mount your mobile phone via "jmtpfs"
* run your backup-scripts (or whatever you wanted to do)
* unmount jmtpfs
* switch back to normal runlevel: # systemctl isolate graphical.target
* log out from console
* go back to graphical session with CTRL + ALT + F7

But this is very cumbersome and you have to close all your running graphical
programs.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 348104] Remove all tags from selected image(s)

2021-03-13 Thread Peter Albrecht
https://bugs.kde.org/show_bug.cgi?id=348104

--- Comment #4 from Peter Albrecht  ---
Just tested this with digiKam version 7.1.0 (AppImage) on Debian 10 Buster
Linux:
I could not find an action / button to remove all tags from all selected
images. So I would say, the feature request is still open.

It has no priority for me, since a workaround exists.

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 196091] Toolbars should allow you to add actions from plugins

2021-03-13 Thread Peter Albrecht
https://bugs.kde.org/show_bug.cgi?id=196091

Peter Albrecht  changed:

   What|Removed |Added

 CC||p...@crazymonkeys.de

--- Comment #5 from Peter Albrecht  ---
Tested with Gwenview version 18.04.0 on KDE Frameworks 5.54.0 and Qt 5.11.3
(Debian 10 Buster):
This feature request is still valid. I can't put commands from the
"plugins"-menu to the toolbar. E.g. "Plugins" > "Export" > "Email Images...".

(But Debian uses quite old versions, so maybe it is fixed with update
developmet)

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 394988] PgDown and PgUp hardcoded in preview mode

2018-06-06 Thread Peter Albrecht
https://bugs.kde.org/show_bug.cgi?id=394988

--- Comment #6 from Peter Albrecht  ---
Thanks! It works great in pre-release
"digikam-6.0.0-git-20180605T154040-x86-64.appimage"!

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 394988] PgDown and PgUp hardcoded in preview mode

2018-06-03 Thread Peter Albrecht
https://bugs.kde.org/show_bug.cgi?id=394988

--- Comment #2 from Peter Albrecht  ---
@Maik:
I use KDE as desktop environment. And I installed Debian Stretch this morning
on this computer. (So I had not much time to change shortcuts. And can't
remember doing so anywhere else then in digiKam.)

I checked my defined shortcuts:
In digiKam there is no other shortcut bound to "PgDown" or "PgUp" then "Next
Image" or "Previous Image". There is no "PgDown" or "PgUp" shortcut defined in
KDE's "Global Shortcuts". But there had been defined shortcuts for
"PgUp"="Previous Page" and "PgDown"="Next Page" in KDE's "Standard Shortcuts".
After removing those, I can no longer scroll in KWrite via PgUp or PgDown. So
the change had some effect. But after restarting digiKam, the behavior is still
like my first comment said: Changing images in "preview mode" leads to the
messagebox: "Ambiguous shortcut detected".

Can you scroll through images in preview mode after having assigned "PgDown" to
"Next Image" while the input focus is on a thumbnail in the thumbnail roll
above the preview image?

For me, switching images via PgDown/PgUp works, if input is in the tag search
box. But it fails, if the focus is on a thumbnail in the thumbnail row above
the preview image.

(Just discovered: Alongside the configured default shortcuts
"space"/"backspace" one can also switch images in preview mode with: Cursor
left/right or cursor up/down - although not explicitly configured)

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 394988] New: PgDown and PgUp hardcoded in preview mode

2018-06-03 Thread Peter Albrecht
https://bugs.kde.org/show_bug.cgi?id=394988

Bug ID: 394988
   Summary: PgDown and PgUp hardcoded in preview mode
   Product: digikam
   Version: 5.9.0
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Usability-Keyboard
  Assignee: digikam-bugs-n...@kde.org
  Reporter: p...@crazymonkeys.de
  Target Milestone: ---

++ Steps to reproduce:

1. in main menu: open "Settings" -> "Configure Shortcuts..."
2. search for "next"
3. set alternate shortcut for "General: Next Image" to "PgDown" (= page down)
4. close settings with "OK"
5. select an image
6. in main menu: select "View" -> "Preview"
7. press the key "PgDown" on the keyboard
-> nothing happens
8. press the key "PgDown" on the keyboard again
-> the following messagebox pops up:

- 8< -
Ambiguous shortcut detected - digiKam

The key sequence 'PgDown' is ambigious. Use 'Configure Shortcuts' from the
'Settings' menu to solve the ambiguity.
No action will be triggert
- >8 -

The same problem exists for "PgUp".


++ Expected behavior:

Pressing "PgDown" should switch from the current previewed image to the next
image in the current album, since I configured this in "Settings" -> "Configure
Shortcuts...".
Pressing "PgUp" should switch from the current previewed image to the previous
image in the current album.


++ Additional information:

Without configuring the shortcut "PgDown" to "Next Image", switching to the
next image in preview mode works fine.

But I need this configured shortcut for my tagging workflow: 
1. open image in preview mode
2. assign tags via keyboard actions
3. switch to the next image (to tag) via keyboard action "PgDown", while input
focus stays in input box "Enter tag here." (I can't use the default "Next
Image" shortcut in this case, since it is "space")

-- 
You are receiving this mail because:
You are watching all bug changes.