Bug #379
Playlist Navigation
| Status: | New | Start Date: | 01/21/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
When multiple videos are queued up in the playlist, I seem to be unable to use the command+left/right hotkeys, nor the menu options under the Playlist menu to move to the previous or next video. They hotkeys are definitely being recognized, as the Playlist menu flashes whenever I press them, but nothing happens in either case.
History
Updated by Hermi G about 1 year ago
I accidentally overlooked this post when I issued bug #388, which covers this issue along with two other bugs.
Note: I am using this post as a location to consolidate information about my patches to MPlayer. Hopefully most of these changes will be adopted by MPE. For the latest information about my MPlayer compilations please visit my new website: https://sites.google.com/site/hermihg/mplayer
Here is a partial list of MPlayer issues addressed by my patched build:
22 118 192 212 247 304 333 362 368 369 375 376 377 378 379 382 383 388 389 390 391 392 393 394 395 397 398 399 400 401 402 403 410
Compiled application: available at my website.
Important: I have only compiled dylibs for the x86_64 architecture, so this will not run on any other arch. I suggest that you read the changelog (bottom to top perhaps), as this will inform you of some new features that you would otherwise not notice.
If you try my build of MPlayer, consider sending me an email to tell me if it works, or more importantly if it doesn't!
I have chosen to version these builds as rev14(1410x), to indicate that this is a completely unofficial release, which does not supersede the next MPE revision.
Update: The task of writing individual tickets for every bug fix and feature I write has become too onerous for me, so 403 will probably be my last ticket until I hear from Adrian. This frees me to document my additions in the changelog, which is much easier to maintain, and allows me to incorporate any changes specific to my builds that won't be propagated back to the official MPE branch without clogging up the issue tracker. Additionally this allows me to avoid the embarrassment of reporting spurious bugs which I myself introduced, which has already happened twice.
Update 2: My new website automatically updates to show the current version based on the sparkle feed, so I don't have to remember to update it. I am therefore now redirecting this page to that site so I don't have to manually update this page for every release.