iceguy wroteThanks! This is great news.
Is this fix now in the version I get by updating with gitpull on runeaudio/dev? Or do I need to make that code change myself?
How do I know what version I am getting/have got? The version number hasn't changed in a year or two! Can I look at some file dates with ssh and "ls -l"?
By the way, the last time I updated a month or so ago, I found some stuff worked that hadn't worked for me before. That included the volume control on the playback display, and some lists that now appear alphabetized, including Playlists and Genres. Well, almost. Country is at the top!
Great work. Thanks again!
thnx - so - yeah - the fix is not in the code base - I see that both the dev and master branches need it - I am running it as a local mod. From what I understand, 2.0 will have a new code base and this issue will be fixed in it, independent of this patch. If you need it now ( like I do, with all those colons in my classical files), then patch away! The way I see it there are two options, one quick and dirty, another more elegant, needs more work on your part.
1) Run it as a local modification (that is, just edit the file) - I am running it like that and so far so good - updating with the git pull may cause conflicts, so I recommend if you want to update, you do a git pull from the command line so you can fix as needed.
2) Fork dev or master, apply the fix and switch RuneUI to that fork. To update (if updates come to the current version) you will need to fetch the upstream and merge into your branch, then pull from your switched RuneUI (at /var/www ).
Re: your other questions, since my point of view is from the github project, I just look at branch (git branch - dev or master) and check the log ( git log) to see what is new and has been fixed. I don't want to talk for the devs, which are brilliant, and also, I am not a Runeaudio dev, just a user that wanted to contribute something, but haven't noticed any tags or markings for versions, so I go from the git info.
Hope this helps.
v
