Many of the patches are a work in progress. For instance, the fading
patch, needs some changes that Bjorn suggested, along with a setting
in the settings menu.

I guess what many of the patches are waiting for are approval by the
"head" developers and user input. If the majority of the users want
something, then usually it will happen.

-eric

F> I'd want to know why the basic and usefull features provided by patches were
F> not included in the main code. I'm actually thinking of the "fade on
F> pause/unpause and stop" and "Changes in F2 screen appearance" as well as
"ffrw: peak meter ->> progress bar", and "One (On) button hold".
F> For info, you can download them here :
F> http://sourceforge.net/tracker/?group_id=44306&atid=439120
F> .. and the process to patch the source is explained in the FAQ (and is a
F> bit difficult to be done by beginners ...)

F> The other patches may need some more testing to be released, but those I
F> gave in example seem to work very well for now ... and on every new CVS
F> version I have to merge them manually because the patch function is not
F> allways a clic-and-run process ;)

F> So my question is : are you thinking of merging those very usefull patches
F> and if so, when do you plan to ?

F> Err ... and the Bookmark patch is not working at all for me. It's because of
F> the difficulty to patch sources well that I'd like most of the stable and
F> tested patches to be merged in the CVS tree ...