>Surely that definition above (in custom.map) is for when in a playlist >or something? And not when playing a track from a browse or something?
I don't really see what you are trying to achieve then. Most people I would assume to be listening to the music they are playing, and therefore on the Now Playing screen, which tells them what they are listening to. If you are off browsing for more music to play, why would you then be thinking of fast forwarding? >From Now Playing, you can scan through the current song by holding down FF or >REW, or by holding down play to jump into the song scanner plugin. If you try to FF or REW a song whilst browsing music, you are jumped to the Now Playing Screen, losing where you were before you did it. The song scanner plugin seems kind of consistent with that approach, except that you can only enter the plugin by manually navigating to it, or by setting up a shortcut to it. All keys can have a different purpose depending what screen you are on. Eg. you don't want play.hold to launch the plugin on any screen, as play.hold is also used to invoke the mixers (when you see an underlined m on any browse screen). As a shortcut has been set up to call the plugin from the now playing screen, that seems a good place to go to when you're done. You can define you own shortcut to enter the plugin from wherever you like using whatever key you want. You may be able to set up a shortcut key within the plugin to take you to some other screen of your choice, but it probably can't tell where you were before you entered the plugin. It may be possible to change the plugin to return to the previous screen when a certain key is pressed (what one would be most sensible?). Patches welcome. _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
