Editing xmls and maki scripts

[ariszlo]

Calvaria, will you check your private messages, please?

[ariszlo]

How do I assign VID and VIS buttons to toggle Equalizer, Frequency response graph or VU meter analog?

What you need is the id's of the containers.

To get the id of the Frequency Response Graph container, open frequency-response-graph.xml and search for container. You will see that its id is "frequency.response.graph".

Now open main-player.xml and find the button you want to toggle the Frequency Response Graph window. Let's say, it is the VIS button. The VIS button has this parameter:

param="guid:{0000000a-000c-0010-ff7b-01014263450c}" 

Replace it with the id of the Frequency Response Graph container like this:

param="frequency.response.graph" 

Now you can toggle the Frequency Response Graph window with the VID button but hovering over the button will still show VID rather than FRG. To fix that you will need to edit button-vid-vis-pe-ml-mute.png with an image editor. Personally, I use GIMP but any other image editor will do that can do transparency and has a color picker and a fill bucket.

There are three instances of each button text. The color of the letters in the first row is #2b3339 and it is #af8a2a in the other rows. The attached png contains the letters for FRG and EQ in a style similar to those used in Quinto.

[ariszlo]

Also the player has the word "Equalizer" on the display...

It is not a button. It is there to tell you whether the equalizer is turned on or off. If you turn the equalizer on by pressing the EQ button in the Equalizer window then the text will turn to light blue.

[Calvaria]

I thought you'd need some special guids to call up those things and was trying to find them.

I turned the Equalizer text into a button, anyway , just like VIS, VID and others, for consistency.
Thank you for the letters!

I have another question, about Play and Pause buttons. The hoverimage and downimaage work well when those buttons are inactive, but when they are active (and they glow brightly in my version) those images are hard to see. For some reason they blend with the active image instead of replacing it. How to make them replace the active image?

[ariszlo]

I have another question, about Play and Pause buttons. The hoverimage and downimaage work well when those buttons are inactive, but when they are active (and they glow brightly in my version) those images are hard to see. For some reason they blend with the active image instead of replacing it. How to make them replace the active image?

It is intentional. In a less sophisticated skin, you just add a line like this to a button tag:

hoverImage="button.minimize.hover" 

With that line added, an active button will look the same as an inactive button when you move the mouse over it. The author of Quinto decided that an active button should always be distinct from an inactive button.

In Quinto, every button has a red hover glow around it but it is hidden by default. It only becomes visible if you hover the mouse pointer over an inactive button. The red hover glow is a layer whose opacity is set to 0 with the following line in 11-hoverglow.m:

glowObject.setXmlParam("alpha","0"); 

And this is how you make it visible:

glowObject.setXmlParam("alpha","255"); 

(alpha="0" stands for zero opacity, i.e. full transparency, alpha="255" stands for full opacity and alpha="127" stands for 50% opacity/transparency.)

To show the hover glow around both active and inactive buttons, you need to simplify the triggerObject.onEnterArea funtion to this:

triggerObject.onEnterArea()
{
    String object_id = triggerObject.getId();
    glowObject.cancelTarget();
    glowObject.setXmlParam("alpha","255");
} 

But if you do so then Quinto will lose one of its cool features.

[Calvaria]

I should have said that I had already introduced hoverimage in all the buttons and that the images I use for hoverimage (and downimage) are completely different from Quinto images. The problem is this: when hoverimage and downimage are activated over an inactive button, they replace the inactive image, that's great. But when they are activated over an active button, they blend with the active image. Is this the internal Winamp feature or Quinto's ? Now my hoverimage and downimage are such, that they can hardly be seen against the glow of the active button (the latter being vastly different from Quinto's active image as well). To be seen they must replace the active image. How to get them to do it?

I would prefer to have separate images for hovered active button and pressed active button, but if not possible , then I'd rather have a distinct hover image (the same for active and inactive) and a distinct down image (the same for active and inactive). So which is the best way to solve this: with hoverimage or with hoverglow.maki or some other way?

[ariszlo]

Without maki, you can show three states of a regular button:

• image
• hoverImage
• downImage

Toggle images also have an activeImage state.

If you are okay with the above states then you might want to comment out all glow layers and all calls of 11-hoverglow.maki like this:

    <!--layer
        x="64" y="0"
        id="mp.button.play.glow.id"
        image="mp.button.play.glow"
        ghost="1"/-->
    <!--script file="SCRIPTS\11-hoverglow.maki" param="mp.button.play.id/mp.button.play.glow.id"/--> 

If you want more then you need maki. Say, you have made an image to show both that the Play button is down and that the mouse pointer is over it. To achieve that, do NOT comment out the glow layers and the calls of 11-hoverglow.maki. You should instead change the following line in elements.xml to point to the image you want to use:

<bitmap id="mp.button.play.glow"    file="PNG\button-playback.png" x="0"   y="78" w="60" h="36"/> 

Then you should edit 11-hoverglow.m to set the alpha value of your image to "255" if it is in the appropriate state. You should make a backup of 11-hoverglow.m before starting to experiment with it. With trial and error, you will finally find out how to modify it to get what you want.

[Calvaria]

Is possible to convert Play and Pause buttons into toggle buttons in order to use activeimage with them?

[ariszlo]

Is possible to convert Play and Pause buttons into toggle buttons in order to use activeimage with them?

I don't think so but there is a workaround. PeterK. does the trick by adding status tags after the button tags.

[Calvaria]

It's still not quite clear to me. You ask me if image, hoverimage and downimage is enough for me. Yes, quite enough (and of course the active image too). So I have them and I have hoverglow.maki disabled. But hoverimage and downimage don't work the way their name suggests: they don't replace the image of the active button, merging with it instead. So I only have partial functionality of hoverimage and downimage – they work only when the button is inactive. Are you saying that to get them to work normally (that is to replace the image of the active button) I must use (modify) glow.maki?

[ariszlo]

Now that you have spent so much time with editing Quinto, I think you will like FrisbeeMonkey's Tutorial. It is a bit outdated but still the best introduction to Winamp skinning.

Most of what you will find there still works. One notable exception is that you can no longer load the containers of the Winamp 3 default skin for your own skin. Another is that the original version of the Play-to-Pause maki is broken. But you can find an updated version here.

[ariszlo]

Do you mean that you want Quinto to show the button states as they are shown in the Winamp Classic skin? Then all you need to do is comment out all the extras added by PeterK. In addition to commenting out all the glow layers and all calls of 11-hoverglow.maki, you should also comment out the status tags immediately below the Play, Pause and Stop button tags.

[ariszlo]

How do you like this skin? My impression is that you are working hard to turn Quinto into something like that.

[Calvaria]

But status contains the definition of the active button, so if I comment it out I will have no active button! I need image, hoverimage, downimage and active image, with hoverimage and downimage replacing active image when hovered over or pressed down. Why do hoverimage and downimage merge with active image, why this strange behavior? Different images (button states) are supposed to replace each other, not merge.

[Calvaria]

This must be somehow connected with the special status of the <status tag and its playBitmap (what does it mean? why not just "image"? This status thing somehow resists being replaced.