Summary: | Usability: Collection management and playlist handling suggestions | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Marcus Thiesen <marcus> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | 1.2-CVS | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Patch for requirement 1
Menu order changed in every occurence of "Append to Playlist" and "Queue After Current Track" Patch correction |
Description
Marcus Thiesen
2005-01-02 15:54:41 UTC
On Sunday 02 January 2005 15:54, Marcus Thiesen wrote:
> 3. This is not really related because it is more or less a real bug: the
> hack you use to open the menu from the menu button on the lower right side
> does not work when the toolbar wraps around, i.e. if the context browser
> half is big enough to make the toolbar wrap, the menu option, which is
> only accesibble over the >> button, does not open up the menu.
Can't confirm this. Works here.
Cool! Did it work well at the party? I must say I'd be nervous to use CVS at a party. It's stability isn't much fun for me. 1. Good suggestion. 2. I agree. Browser double-clicks should perhaps be wholly configurable some place. The same behavious for all browsers though. Will try to implement these one day. I had one crash, but I'm not really sure what the people did to make it crash. Usually I like throwing new audio playback software at people to make some sort of usability test. BTW, I more or less ran only amaroK, without any window manager and anything else fancy. The only thing that makes this a not as good solution is that amaroK still allows to phyically delete files. (I know that I can make them read only, I even did that, but I still think that there might be a --kiosk or --party to make it "safer") Our attitude with regard to the delete menu is that amaroK should be run as a user without write permissions. Afterall it is trivial to delete stuff if the user has write permissions even if amaroK hasn't a delete menuitem. I know it possible to accidently click the menuitem, but everything's a compromise - it was a well requested feature. Anyway you probably don't want the party-guests editing the tags or moving the files with the file-browser either so running KDE as a user with no write permissions to those dirs is your safest bet. Still we could always add the option, but I haven't the time myself, maybe we'll get a patch. Created attachment 9933 [details]
Patch for requirement 1
Implements sequence changing on menus, as required in item 1.
Created attachment 9948 [details]
Menu order changed in every occurence of "Append to Playlist" and "Queue After Current Track"
Created attachment 9951 [details]
Patch correction
Correcting generated patch for application
CVS commit by sellaro: CCMAIL:amarok-devel@lists.sourceforge.net CCBUGS:96164 Added ChageLog note for resolution of bug 96164, part 1 M +2 -0 ChangeLog 1.547 --- kdeextragear-1/amarok/ChangeLog #1.546:1.547 @@ -23,4 +23,6 @@ * GStreamer-engine now uses the "decodebin" autoplugger, which fixes the lag issues that some users had during crossfading. (BR 99570) + * Switched order of "Make playlist" and "Queue after current track" menus + to avoid playlist destruction. (BR 96164 part 1) Part number 2 is a dup of Bug #89727, and it seems nobody could reproduce number 3. Please, avoid reporting many problem in the same bug report, it gets a hell to mantain. :-) |