[digikam] [Bug 463688] New: A stamp tool and gallery?
https://bugs.kde.org/show_bug.cgi?id=463688 Bug ID: 463688 Summary: A stamp tool and gallery? Classification: Applications Product: digikam Version: 7.9.0 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Faces-Recognition Assignee: digikam-bugs-n...@kde.org Reporter: bernd.wech...@gmail.com Target Milestone: --- The good: Face recognition is easily one of the greatest features ever. And the current interface is pretty slick. But what I find is that I go to People, and then Unknown, and then I click on a face and I can enter a name in the box that appears beneath it, and it autocompletes wonderfully to known names and I can click the Check mark and move on. It remembers the name and I can rapidly categorise a series of similar faces in this way. The problem: It's awkward to change between names involves a lot of clicking and typing and moving from mouse to keyboard and back. Improving this workflow would rock. One idea I have is to remove the keyboard needs, so my hand can stay on the mouse. Enter a stamp ,mode and each of the faces in the People list to the left is now a selectable stamp. I can just click the face and now my stamp is for that name. I cab then click all the faces I think belong to that person. I can quickly swap by clicking another. The mouse pointer might look like a stamp and have the name beside it to remind me. Anyhow, just a thought. It keeps the whole workflow with the mouse rapidly clicking faces that I want to stamp with a given name. The terminology of course is not important (to me), this could be use a stamp metaphor to a tag metaphor or a naming metaphor or whatever fits into the Digikam world best. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 359382] Clicking Merged View causes apparent hang (100% CPU use)
https://bugs.kde.org/show_bug.cgi?id=359382 --- Comment #2 from Bernd Wechner <bernd.wech...@gmail.com> --- H, am remote now, but had a quick look. Running the build on a dev machine: 1) It identifies itself as: Amarok Version 2.8-git Using KDE 4.14.2 and was build a few weeks ago from latest pull from github. Can update later today, rebuild and try again. 2) For context I am using an external database on another machine (a media server), and the actual media is stored on a third machine (a NAS). 3) I can navigate my media library just fine in the Media Source panes, all good. Can't play anything, Amarok just falls over (yet to diagnose but I think it's because it fails to find the media file to play trying to access the wrong place because the devices table in the media server isn't consistent with the mounts on the dev server ... I'll fix that later and see). 4) That said, navigating the Local Library works fine. If I click the Merged View button the pane clears eventually refreshes and Amarok seems to hangs still. Take this with a grain of salt until I try on-site as I'm remote now and don't trust the remote connection much (clouds performance experiences with its own lags and issues - using teamviewer). The crucial thing still missing is a clear indication of what Merged View is actually hoping to do though. (As an aside, as I posted on the dev group, I'm still trying to work out how to build on the dev machine and run the binary on the media server - another issue). -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 359382] New: Clicking Merged View causes apparent hang (100% CPU use)
https://bugs.kde.org/show_bug.cgi?id=359382 Bug ID: 359382 Summary: Clicking Merged View causes apparent hang (100% CPU use) Product: amarok Version: 2.8.0 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Collection Browser Assignee: amarok-bugs-d...@kde.org Reporter: bernd.wech...@gmail.com Merged View is poorly documented. I don't know what it does, or is intended to do. The KDE Help Center simply says: Displays the podcasts in a merged or unmerged view. Which tells me little. So I clicked it to see what happens. And it kills the Amarok UI. Linux still responds, even the menu on the Amarok system tray icon still displays, but Amarok responds to nothing. It sits there with 100% CPU usage (I am on a twin core i5 machine) and seems to do so beyond my patience limits so I kill it (with -9) and it doesn't respond to polite request. I restart it and all is good, but if I click the Merged View button again - go to beginning of this report. I have repeated this a third time juts for fun ;-). Now for context I have Local Collection selected when do this and it is hosted on a QNAP NAS and does have over 200,000 tracks in it. Still, the behaviour is puzzling given a lack of clarity as to what this button is actually doing. I'd call this a bug. You may disagree, in which case triage appropriately of course. But at very least I would expect: 1) Better documentation as to what Merged View actually is 2) If the operation is going to take so long a clear progress indicator with cancel option. Lacking either doesn't meet with my expectations as a user I admit. Reproducible: Always Steps to Reproduce: 1. Start Amarok, with a local collection hosted on a network accessed NAS mounted on the local Linux file system, that contains a large number of tracks (> 200,000) 2. On the Media Sources pane navigate to Local Collection 3. Click the Merged View button Actual Results: Amarok UI hangs. Amarok is using 100% of CPU (presumably 1 core of the 2 cores on my box as Linux responds still) Expected Results: Amarok continues to respond If it's an extremely expensive operation: a progress indicator with a cancel option Documentation that describes what to expect (what the heck is Merged View?) -- You are receiving this mail because: You are watching all bug changes.
