![]() |
#41 | |
Junior Member
Join Date: Nov 2010
Posts: 47
|
Quote:
|
|
![]() |
![]() |
![]() |
#42 |
Junior Member
Join Date: Nov 2010
Posts: 47
|
Here's my basic play button. Hover and down images are the same white image with a different alpha, active image is the green one.
|
![]() |
![]() |
![]() |
#43 |
Major Dude
Join Date: Jun 2015
Location: Hungary
Posts: 598
|
This is how you can do it with the Play button:
1. Add your hoverimage to the Play button if you haven't added it yet: PHP Code:
PHP Code:
PHP Code:
Add your hoverimage to the Pause and Stop buttons, too. Comment out the glow layers and 11-hoverglow.maki tags that follow them. Add the script tag calling statuswidth.maki for each button with the necessary changes in param. NOTE. The attached statuswidth.maki works with status images whose width is 60 pixels. If the width of your status images is other than 60 pixels then you will need to edit statuswidth.m and recompile it. |
![]() |
![]() |
![]() |
#44 | |
Major Dude
Join Date: Jun 2015
Location: Hungary
Posts: 598
|
Quote:
And also the status tags immediately following the button tags. |
|
![]() |
![]() |
![]() |
#45 |
Junior Member
Join Date: Nov 2010
Posts: 47
|
No, I have four images: normal (no playback), hover (playback or no playback), down (playback or no playback) and active (playback on). The first three are the same image with a different alpha, making them three different images. The green one is for playback.
|
![]() |
![]() |
![]() |
#46 | |
Major Dude
Join Date: Jun 2015
Location: Hungary
Posts: 598
|
Quote:
1. Add your hoverimages to the Play, Pause and Stop buttons if you haven't added them yet. 2. Remove the status, layer and script tags immediately below the Play, Pause and Stop button tags so that you only have this between <!-- BUTTON "PLAY" - GLOW EFFECT --> and <!-- BUTTON "NEXT" - GLOW EFFECT -->: PHP Code:
PHP Code:
5. Compile pressedbuttons.m and copy it into the scripts folder. |
|
![]() |
![]() |
![]() |
#47 |
Junior Member
Join Date: Nov 2010
Posts: 47
|
In the above approach, if I wanted to have pauseBitmap for the play button, would it be possible to keep the status tag with pauseBitmap (but without playBitmap) or must the whole status be removed?
Could you explain the difference between a basic (regular) play button (coded with image=) and a stopped play button (coded with stopBitmap=)? Can stopBitmap be used for the play button or it only makes sense to use it for the stop button? I didn't understand this, could you explain what you mean? |
![]() |
![]() |
![]() |
#48 | |
Major Dude
Join Date: Jun 2015
Location: Hungary
Posts: 598
|
Quote:
You keep saying that you want to replace one image with the other, not cover it. You cannot replace a button image (image, hoverimage, downimage) with a status image (playBitmap, stopBitmap, pauseBitmap), only cover it. So if it is replace what you want then you should forget about Quinto's status images covering the button images if in the appropriate status. If replace is what you want, then you want this. |
|
![]() |
![]() |
![]() |
#49 | |
Major Dude
Join Date: Jun 2015
Location: Hungary
Posts: 598
|
Status images display playback status (playing, paused, stopped). They are not buttons.
Here are three examples:
Quote:
|
|
![]() |
![]() |
![]() |
#50 |
Junior Member
Join Date: Nov 2010
Posts: 47
|
All right, that's why I couldn't see much difference between stopBitmap in the status of the play button and image="mp.button.play" (and was wondering why stopBitmap existed at all). You mentioned that PeterK did an unusual thing by using status for some buttons, but I didn't understand why it was unusual and was going to ask you about it, because it seemed logical for a button to have a status. Now you have explained it.
So Winamp Modern skin play button doesn't have a status tag, yet does have an active play button image because it's coded in a maki file? So what PeterK did with Quinto is he used status instead of maki, to make things simpler, yet have the same effect? Indeed, with non-transparent buttons it makes a lot of sense, you can have playBitmap and pauseBitmap state and maybe even playBitmap/pauseBitmap+hover/down states (if it's possible to make a suitable mix of non-transparent and partially transparent images). Strange, though, that Winamp doesn't use "activeimage" for the active button state. |
![]() |
![]() |
![]() |
#51 | |||
Major Dude
Join Date: Jun 2015
Location: Hungary
Posts: 598
|
Quote:
Thanks for asking. Now I know more about Winamp Modern. ![]() Quote:
Quote:
Interfaces evolve. Showing playback states on playback buttons is not an idea that automatically comes to mind. Playback status has been shown next to the timer since Winamp 1.0 and probably no developer thought it necessary to introduce a parameter to repeat that info on the playback buttons. Luckily, you can do a lot of things with xml's and maki. |
|||
![]() |
![]() |
![]() |
#52 |
Junior Member
Join Date: Nov 2010
Posts: 47
|
Your pressedbuttons.maki works beautifully, thanks a lot!
Do you know if this function still works in Winamp PHP Code:
|
![]() |
![]() |
![]() |
#53 |
Major Dude
Join Date: Jun 2015
Location: Hungary
Posts: 598
|
As a button action, it does not. It is listed under *** Broken Action (Winamp 5) *** in Wasabi Appendix: Action List.
As a hotkey, it does. Press F5 (or if you have an HP then Fn+F5) to reload the skin. |
![]() |
![]() |
![]() |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|