Albumart.m not correct

[clementj]

I started creating a modified Modern skin by starting with the original "Winamp Modern" skin. My object was to have a skin that would be used by many different people to setup a dance program. The look was not important but removing things that could interrupt dances or cause problems was important. The result "Winamp Modern Folk Dancer" skin was a success, but now I want to modify the Albumart window so it can be locked in place and not inadvertently moved. So I logically started by trying to compile Albumart.m and found that the source was defective, or so old that it was now wrong. Here it is. The statement with the arrow causes the compiler to gag. Can anyone please give me some suggestions on how to fix it, or provide a Winamp5 version that works. The other .m files compile OK.

-------------------------------------------------------------
#include <lib/std.mi>
#include "attribs.m"

Global Container albumart;

System.onScriptLoaded()
{
initAttribs();
albumart = System.getContainer("winamp.albumart");
albumart_visible_attrib.onDataChanged(); <==============
}

albumart_visible_attrib.onDataChanged ()
{
if (getData() == "1")
{
albumart.show();
}
else
{
albumart.close();
}
}

System.onKeyDown(String key)
{
if (key == "alt+a")
{
if (albumart_visible_attrib.getData() == "0")
albumart_visible_attrib.setData("1");
else
albumart_visible_attrib.setData("0");
complete;
}
}

[0x5066]

https://github.com/0x5066/WinampModernPP/blob/WACUPchanges/scripts/albumart.m

You may try having a look here, I haven't tried to compile that one specifically so it may or may not work, but if it doesn't, I'll try to figure out what's going on and fix it.

[clementj]

Thanks, but no go. It doesn't compile. The problem is the line:

albumart_visible_attrib.setData("0");

I think I have the latest std.mi, so I will check attribs.m,

[clementj]

Yup, it was Attribs.

[clementj]

Since you are interested in the Holidays skin I have one with some decorations "Winamp Modern Folk Dancer".

It is designed for various people to create dance lists on the fly, for a dance party. The main features are that it disables or hides many options which can cause dances to be interrupted or have them accidentally rearranged. So, things like shuffle are hidden. It also has a button to prevent windows from being rearranged accidentally. Since our dance programs are done by various volunteers, this is an important button to keep things stable. It is based on the "Winamp Modern" skin. I added buttons for setting the looks of things including decorations and colors. That gives the fiddler something to play with. I have thanksgiving (Harvest), Halloween, Valentine's Day, St. Patrick's Day, Spring and also Holiday plus the possibility of a user contributed decoration and logos. Yes, I borrowed the Holiday decoration, but the others are all my creation, and may be borrowed. The turkey image is from our long-gone family farm, and the cutlery-plates are family heirlooms.

[0x5066]

Yeah I've been following this on and off but never really had a deeper look into it and what scripts it provides, I've been doing my own work on Winamp Modern for WACUP that touches on various minor things and touch ups in places, with adding minor stuff here and there, though I don't think it'll really help you in what you're doing.

Interesting project I must say though, using a Modern Skin to turn Winamp into a dance program, it's impressive!

[clementj]

Most any good player that can make a play list can be used to make a list of dances for a party. The problem is making the list on the fly without interrupting a playing dance. I auditioned a number of players and most had problems. Since various members of the club sign up to program, the player has to be foolproof. So things like the PLAY button or options have to go away. Exit has to be killed when a dance is playing, and single key commands have to be removed so it doesn't go off into never-never land. We need to have a player and dance recordings that are accessible the same way every Friday night. In other words we can' allow the programmer too much diddle freedom.

Sometimes a dance is taught, so we have to play the list and stop at the dance to be taught. So, this needs to be accommodated. Some groups like to play straight through, but others like to stop at each dance and palaver before the next one. There needs to be time between the dances for people to assemble for the next one. For example going from couple, to circle, to lines, or sets needs time between dances. And it is nice to have a delay for starting if the programmer wants to get into a set. When people are fresh and raring to go, we need less time between dances! So we have a unique player with all kinds of features!

A dual library is an important thing, and this can be accomplished by having a tag so the library listing can be switched between active and inactive. Unpopular recordings or no longer danced recordings can be hidden, but brought back when someone wants them. Since recordings have a wide variety of volume, the play gain feature and the automatic setting of it is valuable. Folk Dancers need to hear the music, but do not like very loud volumes so having equal average audibility is very good, and it doesn't kill the dynamics used by the artists.

I am now trying to setup a new laptop with higher resolution than the old one and there are many problems plus demands by the board as to how it should work! I used to have a virgin copy with the setup files of Winamp Modern to help me, but I can't find it now. Ah well I muddle on. I have programmed in a number of languages and can figure out how programs work to fix problems, but am retired and have forgotten all the things I did to create the skin, so now I have to go back and figure it out again.